Meta Description
Connect your own environment to GoedGepickt through the REST API which you can easily use.
Through webhooks you can have data sent from GoedGepickt to your own environments. All users of GoedGepickt have access to our RESTful API.
Some examples where this API can be used for:
- Link your custom made webshop to GoedGepickt
- Link custom functionalities to GoedGepickt
You can also send live updates to your environment through webhooks. You can set this up under Settings -> Webhooks.
**Are you a fulfillment customer of a fulfillment company? Then use the API documentation which can be found here:** [https://documenter.getpostman.com/view/5835145/2s8YCjDXQe](https://documenter.getpostman.com/view/5835145/2s8YCjDXQe)
**Dutch: Ben je een fulfilmentklant van een fulfilmentbedrijf? Gebruik dan de API-documentatie welke hier te vinden is:** [https://documenter.getpostman.com/view/5835145/2s8YCjDXQe](https://documenter.getpostman.com/view/5835145/2s8YCjDXQe)
## Developers
Are you a developer and would you like to test GoedGepickt without making changes to products/product stocks/etc? Please contact us to set up a test account.
---
# Authentication
You can use GoedGepickt API with an API key. Generate a Rest API-key with the instructions below.
## Generating API in the GoedGepickt interface
To create an API key, go to GoedGepickt > Settings -> GoedGepickt API (Dutch: GoedGepickt > Instellingen > GoedGepickt API).
Please fill in a `Key name` (Dutch: `Sleutelnaam`) to indentify your keys and click on `Create key` (Dutch: `Sleutel aanmaken`)
## Using authentication headers
Any call to the GoedGepickt APIs should be authenticated with following request header:
- `Authorization: Bearer` - The API key of your GoedGepickt account
---
## Request/Response Format
The default response format is JSON. Requests with a message-body use plain JSON to set or update resource attributes. Successful requests will return a `200 OK` HTTP status.
---
## Rate limiting
To prevent overload we use rate limiting. There is a limit of 150 requests per IP over all endpoints. Details of your use of the rate limits can be found in the following headers:
| **Header name** | **Description** |
| --- | --- |
| Retry-After | When a 429 error is encountered here you can find when the limit will be reset and you can retry your request. The value given is in seconds. |
| X-Ratelimit-Limit | The amount of request possible within a minute |
| X-Ratelimit-Remaining | The amount of requests remaining untill the rate limit is reached |
| X-Ratelimit-Reset | A timestamp where you can indicate when the rate limit will reset |