Environments
| Environment | Base URL | Use it for |
|---|---|---|
| Test | https://api-test.e-parcel.fi |
Development, automated tests, trying things out |
| Production | https://api.e-parcel.fi |
Real shipments only |
Each environment has its own API keys: a test key does not work on production
and the other way round. This portal is served by each environment at
/developers/, and its interactive reference sends
requests to the environment you are reading it on.
Client settings
Section titled “Client settings”| Setting | Value |
|---|---|
EPARCEL_BASE_URL |
Make it configuration, never a constant. Test while developing, production when live. |
EPARCEL_API_KEY |
One per environment, sent as Authorization: Bearer <key>. |
| HTTP timeout | 60 seconds for single creates. The server can spend up to about 25 seconds trying carriers before it answers, so a short client timeout turns successes into “unknown”. |
| Batch size | Up to 500 parcels per batch, but a batch has no server-side deadline. Start with batches of about 50, measure, and keep each batch well inside your timeout. |
Rate limits
Section titled “Rate limits”No rate limit is published. Send creates as orders become ready to ship, use the batch endpoint for bulk runs, and don’t fan out hundreds of parallel single creates.
Health checks
Section titled “Health checks”GET /health reports that the service is up. GET /readyz also checks the
database. Neither needs authentication.