Endpoints and requests
Rechain API endpoints are organized by resource type. You’ll need to use different endpoints depending on your requirements. All API endpoints follow this pattern:https://api.rechain.co/public/v1/{resource}
Example POST request
Example POST request
Create a new product.
This example illustrates how to create a new product using the
Product resource and the POST /public/v1/products endpoint. Replace token with the access token you generated in the Authentication section.Example GET request
Example GET request
Retrieve a product.
This example illustrates how to find a new product using the
Product resource and the GET /public/v1/products/:id endpoint. Replace token with the access token you generated in the Authentication section.Example PUT request
Example PUT request
Update a new product.
This example illustrates how to update an existing product using the
Product resource and the PUT /public/v1/products/:id endpoint. Replace token with the access token you generated in the Authentication section.Example DELETE request
Example DELETE request
Delete a product.
This example illustrates how to delete an existing product using the
Product resource and the DEL /public/v1/products/:id endpoint. Replace token with the access token you generated in the Authentication section.Rate limits
The Rechain API supports a limit of 100 requests per account per minute.Usage limitations
The Rechain API supports a limit of 100 requests per minute. Past the limit, the API will return a429 Too Many Requests error.
All API responses include the X-Rechain-Api-Call-Limit header, which shows how many requests the client has made, and the total number allowed per minute.
A 429 response will also include a Retry-After header with the number of seconds to wait until retrying your query.