> ## Documentation Index > Fetch the complete documentation index at: https://onlytraffic.com/docs/llms.txt > Use this file to discover all available pages before exploring further. # RevShare-транзакции > Financial transactions on your RevShare campaigns. Only RevShare is covered here — CPL subscribers trigger separate settlement events, not per-transaction revenue. ## OpenAPI ````yaml api/openapi-partners.json GET /api/marketer/revshare/transactions openapi: 3.0.2 info: title: OnlyTraffic Marketer API version: 2.1.0 description: >- Partner (marketer) API for OnlyTraffic. **Authentication:** pass your API key in the `Authorization` header (`Authorization: your-api-key` or `Authorization: Bearer your-api-key`). Create keys in the partner cabinet: Tools -> API (https://partners.onlytraffic.com/tools/api). Up to 5 named keys per account, each **Full** or **Read-only**, with an optional expiry. Keys start with `ot_partners_` and are shown once, at creation. Read-only keys cannot call the `POST` endpoints (`error_code` 403, message `This API key is read-only`). An older legacy key keeps working with full access until you delete it on the same page. **Pagination:** all list endpoints accept `offset` (default 0) and `limit` (default 50, max 1000) as query parameters or JSON body fields. **Dates:** every timestamp field has two variants — an ISO 8601 string (`*_at`) and a Unix timestamp integer (`*_at_ts` / `*_ts`). **Writes:** a Full-access key reads and writes. Write endpoints are `POST` with a JSON body, accept public ids only (`revc_…`, `cplo_…`) and answer with the updated object in `data`. Rate limit: 120 requests per minute for reads, 30 per minute for writes, per account (shared by all its keys). servers: - url: https://partners.onlytraffic.com security: [] tags: - name: RevShare description: RevShare campaigns and financial data - name: CPL description: Cost-Per-Lead orders placed against your offers - name: CPC description: Cost-Per-Click orders and the category catalog - name: Subscribers description: Fans acquired through your campaigns - name: Stats description: Dashboard-style statistics widgets (fans, income, conversion) - name: Write description: >- Write API: start / stop / update campaigns and accept / reject / stop CPL campaigns (same key, same rules as the cabinet) paths: /api/marketer/revshare/transactions: get: tags: - RevShare summary: List RevShare transactions description: >- Financial transactions on your RevShare campaigns. Only RevShare is covered here — CPL subscribers trigger separate settlement events, not per-transaction revenue. parameters: - $ref: '#/components/parameters/offset' - $ref: '#/components/parameters/limit' - name: of_account_id in: query schema: type: integer description: Filter by OnlyFans account numeric id. - name: campaign_id in: query schema: type: string description: Filter by campaign public_id. - name: from in: query schema: type: string format: date example: '2024-01-01' description: Start date (inclusive), format Y-m-d. - name: to in: query schema: type: string format: date example: '2024-01-31' description: End date (inclusive), format Y-m-d. - name: status in: query schema: type: string enum: - processed - refunded description: Filter by transaction status. responses: '200': description: Success content: application/json: schema: oneOf: - title: Success type: object properties: status: type: string enum: - success data: type: array items: $ref: '#/components/schemas/RevShareTransaction' - $ref: '#/components/schemas/ErrorResponse' example: status: success data: - of_transaction_id: '9876543210' of_user_id: 789 of_user_name: John of_account_id: 456789 campaign_id: camp_abc123 amount: 10.5 revenue: 4.2 type: tip status: processed is_refunded: false refunded_at: null refunded_at_ts: null date: '2024-06-01T12:00:00+00:00' date_ts: 1717243200 security: - api_key: [] components: parameters: offset: name: offset in: query schema: type: integer default: 0 minimum: 0 description: Number of records to skip. limit: name: limit in: query schema: type: integer default: 50 minimum: 1 maximum: 1000 description: Number of records to return. schemas: RevShareTransaction: type: object properties: of_transaction_id: type: string description: Original OnlyFans transaction id. of_user_id: type: integer description: OnlyFans subscriber user id. of_user_name: type: string description: Subscriber display name at transaction time. of_account_id: type: integer campaign_id: type: string amount: type: number description: Gross transaction amount (what the subscriber paid). revenue: type: number description: Your share of the transaction. type: type: string enum: - subscription - resubscription - tip - message - post - stream - other description: OnlyFans transaction type. status: type: string enum: - processed - refunded is_refunded: type: boolean refunded_at: type: string format: date-time nullable: true refunded_at_ts: type: integer nullable: true date: type: string format: date-time date_ts: type: integer ErrorResponse: title: Error type: object properties: status: type: string enum: - error message: type: string description: Human-readable error description. error_code: type: integer description: >- 403: access denied (missing / unknown / expired / revoked key, or the account is not an active partner: `Error! Access denied`; a Read-only key calling a write endpoint: `This API key is read-only`). 404: not found. 422: bad request params (message says what is wrong). 429: rate limit exceeded (a `Retry-After` header is set) or another campaign start is still running. 500: server error. 503: the platform did not answer a write in time, retry later. securitySchemes: api_key: type: apiKey name: Authorization in: header description: >- API key from the partner cabinet, Tools -> API (https://partners.onlytraffic.com/tools/api): up to 5 named keys per account, each Full or Read-only, `ot_partners_` prefix, shown once at creation. Raw value or `Bearer` form. Read-only keys cannot call the `POST` endpoints (403 `This API key is read-only`); expired or revoked keys get 403 `Error! Access denied`. ````