# Enterprise (/docs/enterprise) Prepare a SocialCrawl security, scale, reliability, support, compatibility, and procurement review Enterprise evaluation starts with the workload you intend to run. Send enough detail for SocialCrawl to answer against that workload instead of asking you to evaluate a generic feature list. ## What should I include in an Enterprise request? Send the following through [Contact](/contact): - The endpoints and platforms you expect to use. - Expected request volume, peak concurrency, and any scheduled bursts. - The countries or regions where your systems and users operate. - Your retention and deletion requirements. - Your API-key and access-control requirements. - Your security, privacy, and legal-review questions. - Your target test, procurement, and production dates. If you already have a failing or slow request, include its `request_id`. Do not include an API key, webhook secret, or social-platform credential. ## Security and data handling Start with [Security](/docs/security.md). It documents the request path, the public-data boundary for social-platform collection, current retention categories, API-key handling, webhook verification, international-transfer language, and the difference between infrastructure-provider attestations and product-level assurance. For a review, identify the exact documents and answers your organization requires. SocialCrawl will confirm what is currently available. Do not treat a provider certificate, this page, or general privacy language as a substitute for a document your process requires. The current published legal documents are: - [Privacy Policy](/legal/privacy-policy) - [Terms and Conditions](/legal/terms-and-conditions) - [Public Data Notice](/legal/public-data-notice) ## Access and key controls SocialCrawl authenticates API requests with the `x-api-key` header. Keep keys on your server, create a separate key for each environment or service, and rotate by deploying a replacement before revoking the old key. API keys are not permission-scoped. An active key can call the API surface available to its account. A per-key credit limit controls spend, not endpoint access. Record any additional access-control requirement in your Enterprise request so SocialCrawl can answer it explicitly. See [Authentication](/docs/authentication.md) for key creation, expiry, caps, revocation, and rotation. ## Scale and reliability Describe both steady traffic and bursts. Request rate and concurrent work are separate constraints, so provide both values rather than one average request count. Use the current public contracts as the baseline: - [Rate limits](/docs/rate-limits.md) explains request-rate and concurrency controls and their response headers. - [Production checklist](/docs/production-checklist.md) covers endpoint-specific timeouts, bounded retries, idempotency, pagination, caching, spend controls, and request logging. - [Reliability](/reliability) describes the operating model. - [Status](/status) shows current service health. Do not infer a custom limit, historical uptime percentage, recovery objective, or continuity commitment from those pages. Put any required threshold or contractual commitment in the request for explicit confirmation. ## Support For a logged, non-streaming request, retain the `request_id`, endpoint, HTTP status, `error.type`, response credit fields, cache state, and your own timestamps and attempt count. This gives support the correlation details available for that operation without receiving your secret. Streaming requests do not currently create the same request-log row, so include your own timestamps and client logs when reporting them. Use [Status](/status) for current service state and [Contact](/contact) for account, procurement, or security-review questions. No service-level agreement is committed by the current published self-serve or Enterprise material. If an SLA is required, include it as a requirement and obtain explicit written confirmation of what is available. ## Schema compatibility The canonical schema is the integration boundary. Published `/v1` schema identifiers remain backwards-compatible, while new optional fields can be added. Consumers should ignore unknown fields and validate the fields they use. Review both contracts: - [Schema compatibility](/docs/schema-compatibility.md) explains which response-shape changes are compatible. - [Versioning and deprecation](/docs/versioning.md) explains the API lifecycle and notice process. Use the [Changelog](/changelog) to review published changes during evaluation and after release. ## Procurement checklist List the endpoints, expected pages or calls, and worst-case retry or pagination behavior before estimating spend. Endpoint costs differ, and a list operation can bill once per page. - [Credits](/docs/credits.md) explains holds, settlement, cache hits, replays, and returned billing fields. - [Endpoint pricing](/docs/endpoint-pricing.md) is the current endpoint-level pricing reference. - [Testing your integration](/docs/testing-your-integration.md) shows how to isolate and cap non-production testing. For procurement, bring a checklist rather than an assumed answer: - Required data-flow and public-source description. - Retention and deletion requirements by data category. - Current product certification status and required assurance or review materials. Ask SocialCrawl to confirm the current status; infrastructure-provider attestations are not product certification. - Current DPA availability, required data-processing terms, and operating regions. Ask SocialCrawl to confirm availability; this page does not represent a DPA. - Expected rate, concurrency, and workload schedule, checked against the published [Rate limits](/docs/rate-limits.md). - API-key and access-control requirements. - Pricing and billing model to be evaluated. - Required support and service-level terms. - The current [Privacy Policy](/legal/privacy-policy), [Terms and Conditions](/legal/terms-and-conditions), and [Public Data Notice](/legal/public-data-notice). SocialCrawl will confirm each item against the current product and any proposed agreement. A requirement in this list is not a claim that the capability or document is available. ## Get started [Contact SocialCrawl](/contact) with the request packet from the first section. If you are still validating the API surface, start with [Testing your integration](/docs/testing-your-integration.md), then use the [Production checklist](/docs/production-checklist.md) before release. - [Security](/docs/security.md): Review request flow, data handling, keys, webhooks, and assurance boundaries. - [Production checklist](/docs/production-checklist.md): Prepare retries, pagination, caching, spend controls, and request tracing. - [Schema compatibility](/docs/schema-compatibility.md): Understand the backwards-compatible contract for published schemas. - [Changelog](/changelog): Review published API and product changes.