Public API Terms of Use
Terms governing access to, integration with, and use of the Growth Station public API.
Growth Station — Public API Terms of Use (v1)
Last updated: April 14, 2026
Translation notice: This English version is provided for convenience. If it conflicts with the original Portuguese document, the Portuguese version prevails.
These API Terms of Use ("API Terms") govern access to and use of the Public API made available by Growth Machine Editora e Aceleração Ltda. ("Growth Machine") as part of the Growth Station platform.
By using the Public API, the developer or company (the "Integrator") agrees to these API Terms. These API Terms supplement the Platform's general Terms of Use.
1. Definitions
| Term | Meaning |
|---|---|
| Public API | The REST application programming interface made available by Growth Station for integration with external systems. |
| API Key | A unique credential generated for a Project to authenticate API requests. |
| Rate Limit | The maximum number of requests permitted during a specified period. |
| Integrator | The individual or legal entity that uses the Public API to integrate systems with Growth Station. |
| Project | A business account in Growth Station to which an API Key is linked. |
2. API Access
2.1 Authentication
- API access requires a valid API Key generated in the Project settings.
- The API Key must be included in the
Authorizationheader of each request. - Each API Key is linked to a single Project and provides access only to that Project's data.
2.2 Key Generation and Management
- Only Users with the Admin role can generate API Keys.
- A Project Admin can revoke an API Key at any time.
- API Keys should be rotated periodically, at least once a year.
3. Available Endpoints
The Public API v1 includes the following resources, subject to change:
| Resource | Operations | Description |
|---|---|---|
| Leads | Create, list, retrieve, update | Programmatic lead management |
| Prospecting routines | Add a Lead to a routine | Add Leads to prospecting routines |
| Webhooks | Create, list, delete | Configure webhook endpoints |
| Custom fields | List | Retrieve Project custom fields |
Complete and current documentation is available in the developer portal.
4. Rate Limits
4.1 Limits
| Type | Limit |
|---|---|
| Requests per minute | According to the subscribed plan (default: 200 requests/minute) |
| Requests per hour | According to the subscribed plan |
| Requests per day | According to the subscribed plan |
4.2 Exceeding a Limit
- Requests exceeding a rate limit receive an HTTP 429 (Too Many Requests) response.
- The
Retry-Afterheader indicates the recommended waiting period. - Repeatedly exceeding limits may result in temporary suspension of the API Key.
4.3 Rate-Limit Headers
Each response includes:
| Header | Description |
|---|---|
X-RateLimit-Limit | Maximum number of requests during the period |
X-RateLimit-Remaining | Requests remaining during the period |
X-RateLimit-Reset | Timestamp when the period resets |
5. Integrator Responsibilities
The Integrator must:
- Protect API Keys — Treat them as confidential credentials and never expose them in client-side code, public repositories, or logs.
- Comply with rate limits — Implement exponential backoff and honor the
Retry-Afterheader. - Validate data — Ensure that data sent to the API is valid, current, and lawful.
- Comply with the LGPD — Maintain an appropriate legal basis for personal data sent through the API and respect data subject rights.
- Maintain security — Use HTTPS for every integration and protect data received from the API.
- Monitor usage — Detect and correct anomalous integration behavior.
6. Prohibited Use
The following uses are expressly prohibited:
- Sharing or reselling API access without Growth Machine's authorization.
- Exploiting vulnerabilities — Conducting security testing, penetration testing, or scanning without prior written authorization.
- Overloading the API — Intentionally sending request volumes that exceed limits or impair service for other Users.
- Scraping or data mining — Using the API for bulk data extraction beyond the contracted scope.
- Malicious automation — Using bots to create false Leads, spam, or abusive content.
- Circumventing rate limits — Using multiple API Keys or IP addresses to evade limits.
- Unauthorized intermediation — Creating services that re-expose the API to third parties.
7. Data and Privacy
7.1 Data Sent Through the API
- Personal data of Leads created or updated through the API is subject to the Platform's Privacy Policy and DPA.
- The Integrator is responsible for maintaining a legal basis for processing personal data sent through the API.
- Data created through the API is stored and processed under the same security measures as data created through the user interface.
7.2 Data Received Through the API
- The Integrator must protect data received from the API with appropriate security measures.
- Data received from the API may be used only for purposes authorized by the Project.
7.3 Webhooks
- Webhook endpoints configured through the API must use HTTPS.
- The Integrator is responsible for keeping its endpoints available and secure.
- Webhook payloads are signed with HMAC using the
X-GS-Engage-Signatureheader and must be validated by the Integrator.
8. Availability and Service Levels
- Growth Machine will use reasonable efforts to keep the API available but does not guarantee 100% availability.
- Planned maintenance will be communicated in advance where reasonably possible.
- The API may be temporarily unavailable because of updates, maintenance, or force majeure.
- The Integrator must implement error handling and retry logic.
9. Versioning
- The Public API is versioned through its URL, for example
/api/v1/. - Previous versions will be maintained for 6 (six) months after a new version is released.
- Breaking changes will be announced at least 30 (thirty) days in advance.
- The Integrator must migrate to new versions within the deprecation period.
10. Intellectual Property
- The API, its documentation and specifications, and all associated intellectual property belong to Growth Machine.
- API use does not grant the Integrator any intellectual property ownership rights.
- The Integrator may refer to "Growth Station" in descriptions of its integration in accordance with applicable brand guidelines.
11. Suspension and Revocation
Growth Machine may suspend or revoke API access:
- For a breach of these API Terms.
- For abusive or fraudulent use.
- When use presents a security risk to the Platform or other Users.
- When the Project is delinquent in its payments.
- At the request of a Project Admin.
Revocation will be communicated to the Project with reasonable advance notice, except where an immediate risk exists.
12. Limitation of Liability
-
Growth Machine is not liable for:
- Damage caused by API interruptions.
- Decisions made based on data obtained through the API.
- Failures in integrations developed by the Integrator.
- Data loss resulting from misuse of the API.
-
Growth Machine's aggregate liability is limited as set out in the Platform's general Terms of Use.
13. Changes
- Growth Machine may amend these API Terms at any time.
- Material changes will be announced at least 15 (fifteen) days in advance.
- Continued API use after an amendment takes effect constitutes acceptance of the amended terms.
14. Support
- Documentation: developers.growthstation.app
- Technical support: suporte@growthedge.com.br
15. General Provisions
- These API Terms supplement and form part of the Platform's general Terms of Use.
- If these API Terms conflict with the general Terms of Use, the general Terms of Use prevail.
- The laws of the Federative Republic of Brazil apply, and the forum specified in the general Terms of Use has jurisdiction.
These API Terms of Use were prepared based on Brazilian law.
Your feedback matters
Did this guide answer your question?
It only takes a few seconds and helps us keep the knowledge base useful.