Technical Resources
Prior to start integrating and testing, it's necessary to have three components in hand, that needs to be provided by our team.
| Key | Sample value | Used for |
|---|---|---|
| public key | a23271e1-c1c0-44d3-4567-5610217d1151 | Tokenizing cards using the javascript library |
| client id | MY_CLIENT_ID | client id to be used during the oauth authentication |
| client secret | 4efa3460-a121-1ca9-abcd-e1345ff5510d | client secret to be used during the oauth authentication |
It's also important to take note of the following resources:
| Resource | URL |
|---|---|
| Static javascript component | https://cdn.simpleps.com/production/inyo.js |
| OpenAPI specs | https://{FQDN}/q/swagger-ui |
| Resource | Sandbox | Production |
|---|---|---|
| API endpoint | https://{FQDN}/ | https://{FQDN}/ |
| Postman | Upon request |
Considerations: During the key generation, it will be required by our team the url of the origin server used for development and production. This origin url will ensure that communications in between the browser and our servers are allowed, per CORS rules.
Rate Limits
Each client is allotted a standard amount of requests per minute, that can be reviewed based on specific scenarios.
You must implement techniques such as exponential backoff, and be ready to deal with HTTP 429 responses.
| Resource | Limit (Requests/Minute) |
|---|---|
| Authentication | 60 |
| Rates | 200 |
| All other authenticated requests | 400 |