Getting Started
This guide will help you quickly get started with the PinkCloudSync service.
Prerequisites
Before you begin, make sure you have:
- An active PinkCloudSync account
- API key and secret (obtain from the console)
- Basic knowledge of REST APIs
- An installed tool for working with APIs (curl, Postman, or Python)
Quick Start Checklist
Follow these steps to get started:
- Create a PinkCloudSync account
- Obtain API keys from the console
- Make your first authentication request
- Test API access with a simple query
- Review rate limits and best practices
Obtaining API Keys
To work with the API, you'll need an API key and secret1.
- Log in to the PinkCloudSync console.
- Navigate to the API Keys section.
- Click Create New Key.
- Save the API key and secret in a secure location.
Important
The API secret is displayed only once during creation. If you lose it, you'll need to create a new key.
Base API URL
All API requests are sent to the base URL:
1 | |
For testing, use the sandbox environment:
1 | |
First Request
Let's make your first API request — obtaining an access token.
1 2 3 4 5 6 | |
1 2 3 4 5 6 7 8 9 10 11 12 13 | |
Response
1 2 3 4 5 | |
The "expires_in" field indicates the token lifetime in seconds (3600 = 1 hour).
Using the Token
The obtained token is used to authenticate all subsequent requests. Add it to the Authorization header:
1 2 | |
1 2 3 4 5 6 7 8 9 10 | |
Rate Limits
PinkCloudSync API applies the following rate limits:
| Request Type | Limit |
|---|---|
| Authentication | 10 requests per minute |
| Sync Operations | 100 requests per minute |
| Data Reading | 1000 requests per minute |
When the limit is exceeded, the API returns a 429 Too Many Requests error. Response headers contain information about limits:
X-RateLimit-Limit— maximum number of requestsX-RateLimit-Remaining— remaining number of requestsX-RateLimit-Reset— counter reset time (Unix timestamp)
Troubleshooting
401 Unauthorized Error
If you receive a 401 Unauthorized error, check:
- Correctness of the API key and secret
- Token expiration (tokens are valid for 1 hour)
- Presence of the
Authorizationheader in the request
Example error response:
1 2 3 4 | |
429 Too Many Requests Error
If you've exceeded the rate limit:
- Check the
X-RateLimit-*headers in the response - Wait for the counter reset (time specified in
X-RateLimit-Reset) - Optimize request frequency
Response headers:
1 2 3 | |
Best Practices
To avoid common issues:
- Store credentials securely — Use environment variables or secure vaults
- Implement token refresh — Request new tokens before expiration
- Handle rate limits — Implement exponential backoff
- Log errors properly — Never log sensitive data like tokens
Next Steps
Now that you've set up API access, explore the following sections:
- Authentication — learn more about working with tokens
- Data Synchronization — creating sync sessions
- Conflict Resolution — resolving data conflicts
-
API keys consist of two parts: a public key (starts with
pk_) and a secret key (starts withsk_). Never share your secret key. ↩