Regarding POST /api/public/rates
How to specify id/uid in a POST request | When sending data, you can use either "id" or "uid" as the identifier. You can check the two ways of specifying the identifier, "how to specify using id" and "how to specify using uid," by switching the dropdown menu on the API documentation screen. |
Response specifications for GET request (/rate_plans/{id}) | When you execute GET /rate_plans/{id} to retrieve rate plan information, the returned data includes both "id" and "uid" fields. |
Handling of cases where the UID is not set | Even if the relevant data does not have a "uid" set, it will not result in an error; the "uid" field will simply contain null (an empty value) to indicate that "no value exists." |
FAQ
Regarding recovery after the feed retention period (7 days) has been exceeded.
Q. If the feed retention period of 7 days is exceeded, how should the system be restored?
A. Feed events older than 7 days cannot be recovered.
Q. Is it possible to increase the current API access limit of 120 requests per minute per partner? A.
Currently, it is not possible to lift this limit for individual integrations.
However, you can reduce the load on API requests in the following ways.
Use a request queue to distribute processing.
Expand the scope of data retrieved in a single query.
Implement a retry process if the rate limit is reached.