Cito API

Cito API webhooks

Create and manage webhooks with your API key. A key only reaches webhooks on its own account. GET /webhooks/events lists every event with real examples.

Data & analytics#sports--fitness

Fork copies the collection into your workspace, without the publisher's secrets, so you can add your own key and send requests. Star saves it to your starred APIs (Account › Marketplace) and helps others find it.

Overview

Create and manage webhooks with your API key. A key only reaches webhooks on its own account. GET /webhooks/events lists every event with real examples.

Endpoints 22

  • GETEvery webhook event, for every game/webhooks/eventsPublic. Each event has a description, when it fires, its status (active, quiet, not_observed), measured frequency, minimum plan, filters, field names and a…
  • GETList your webhooks/webhooks
  • POSTCreate a webhook/webhooksPro or Scale. The secret is returned once. The account owner is emailed when a webhook is created with an API key.
  • GETOne webhook (never the secret)/webhooks/:id
  • DELETEDelete a webhook/webhooks/:id
  • PATCHChange URL, events, filters or isActive/webhooks/:idChanging the URL with an API key emails the account owner.
  • POSTSend a test delivery and get a diagnosis/webhooks/:id/testNo body: a short test ping. {"event":"cs2.match.completed"}: a real recent sample of that event, signed, marked test: true, data.test: true and X-Cito-Test:…
  • POSTReplace the signing secret (returned once)/webhooks/:id/regenerate-secret
  • POSTClear failures and turn the webhook back on/webhooks/:id/reset
  • POSTClear failures on all your webhooks/webhooks/reset
  • GETDelivery log, newest first/webhooks/:id/deliveries
  • GETOne delivery with its payload/webhooks/:id/deliveries/:deliveryId
  • POSTRe-send a stored event or a match/webhooks/:id/replaySends to your own webhook only, marked data.replayed true and data.original_event_id. At most 10 events per call.
  • POSTRe-send the match and result events you missed/webhooks/:id/catch-upEvents that failed or were skipped during a pause and were never delivered, oldest first. Live ticks are skipped. Stops at the first failure.
  • GETList your live inboxes/webhook-inbox
  • POSTCreate a hosted temporary test inbox/webhook-inboxAny plan. Lasts 24 hours. Holds 100 requests of up to 64 KB. Free and Starter can add samples; pointing a webhook at it needs Pro or Scale.
  • DELETEDelete an inbox/webhook-inbox/:id
  • GETRead stored requests/webhook-inbox/:id/requestsNewest first. With after=<latestRequestId> only newer ones, oldest first, for polling.
  • DELETEClear stored requests/webhook-inbox/:id/requests
  • GETServer-sent events, one per stored request (closes after 5 minutes; reconnect)/webhook-inbox/:id/stream
  • POSTPut a real sample of an event into the inbox/webhook-inbox/:id/sampleAny plan, any event, signed with the inbox secret and marked as a test. Below Pro, samples are at least 2 hours old. Up to 30 an hour.
  • POSTReceive a request (the inbox url)/webhook-inbox/:tokenPublic: the token is the access. Answers without echoing the body. Nothing is forwarded. A request without a valid signature is kept only in a small separate…

API details

Base URL
https://api.citoapi.com/api/v1
Authentication
An API key in the x-api-key header
A bearer token in the Authorization header
Operations
22 operations on 17 pathsPOST 10GET 8DELETE 3PATCH 1
Response formats
application/json
Description format
OpenAPI 3.0.3, API version 1.0.0

How to test the Cito API webhooks in Swastik Codes

  1. Open the APISelect “Fork & run in Swastik Codes” on this page. Sign in or create a free account if asked.
  2. Fork it into your workspaceChoose a workspace. You get your own copy of the Cito API webhooks collection, without the publisher's secrets.
  3. Add your credentialsThis API uses an API key in the x-api-key header. Add yours in the collection's variables or an environment; the requests already reference it.
  4. Send a requestPick an endpoint, for example “Every webhook event, for every game” (GET /webhooks/events), and press Send. Check the response, add tests and run the whole collection with the runner.

Frequently asked questions

What is the Cito API webhooks?

Create and manage webhooks with your API key. A key only reaches webhooks on its own account. GET /webhooks/events lists every event with real examples. It is listed under Data & analytics and has 22 endpoints.

Who publishes the Cito API webhooks?

It is listed from Cito API's public API description (an OpenAPI document), not published by Cito API on Swastik Codes. Anyone who controls citoapi.com can claim the profile by adding a DNS TXT record.

What is the base URL of the Cito API webhooks?

Requests go to https://api.citoapi.com/api/v1. Endpoint paths are added to this base URL.

How do I authenticate with the Cito API webhooks?

It accepts 2 methods: an API key in the x-api-key header; A bearer token in the Authorization header.

How many endpoints does the Cito API webhooks have?

22 operations on 17 paths (10 POST, 8 GET, 3 DELETE, 1 PATCH).

Is forking the Cito API webhooks free?

Yes. Forking copies the collection into your workspace for free. It has been starred 0 times and forked 0 times.

Suggest an API

Tell us which public API is missing. We check it, then add it here with its endpoints when it has an OpenAPI (Swagger) description.