● REST API · Webhooks · Custom API

For developers: connect to our products in code.

Q: How do I get an API key?

Tell oigoworks which product you want to connect to and why; a key is created for your company and sent with the endpoint list and examples.

Q: Are there rate limits?

Yes; public endpoints are rate limited. For high-volume use the limits are tuned to the customer's needs.

Our products talk to other systems through JSON REST APIs and webhooks. If the endpoint you need doesn't exist yet, we build it for your project.

Request API access → See available APIs

JSON · Bearer API key · data isolated per company · HTTPS

terminal · oigodesk REST API ● 201 Created

# Create a support ticket (example)
curl -X POST https://<your-domain>/api/v1/tickets \
  -H "Authorization: Bearer $OIGODESK_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "title": "Billing address needs updating",
    "priority": "high",
    "contact_email": "customer@example.com",
    "contact_name": "Jane Doe"
  }'

REST · JSON Bearer API keys Webhook receivers Cross-product bridges Custom API development

Who is it for?

Teams connecting their own software.

If you run in-house software, a mobile app or a customer portal, you can connect it to oigoworks products through the API: open support tickets from your own screens, check their status, embed live chat on your site, or react to payment and channel events.

Every request is authenticated with an API key that belongs to your company and only reaches your company's data. Our products talk to each other the same way — oigohotel, for example, opens oigodesk tickets matched by hotel ID.

If you need an endpoint that isn't available yet, we build it, with documentation and a test environment.

Available APIs

APIs you can use today.

These endpoints run in our products.

oigodesk REST API

Manage support tickets from your own system.

List tickets (filter by status)
Create, read and update tickets
List and add comments

◌

Live chat API

Embed oigodesk live chat in your site or app.

Start a session
Send and list messages
Leave an offline message

✉

Email to ticket

Emails sent to your company's inbound address become tickets automatically.

Per-company inbound address
Attachments saved to the ticket
Auto-reply and bounce filtering

MethodEndpointDescription

GET/api/v1/ticketsLists tickets; filter with status.

POST/api/v1/ticketsOpens a ticket: title, description, type, priority, contact.

GET/api/v1/tickets/{id}A single ticket's details.

PATCH/api/v1/tickets/{id}Updates status, priority or assignee.

GET/api/v1/tickets/{id}/commentsThe ticket's comments.

POST/api/v1/tickets/{id}/commentsAdds a comment to the ticket.

Webhooks & bridges

The moment it happens.

Our products receive events from external services via webhooks, instantly — no polling. Incoming requests are verified with each service's own method (signature or verification token).

⇄ Channel manageroigohotel: booking notifications from SiteMinder and HotelRunner.

✉ WhatsApp & InstagramMessages from Meta land in the oigohotel and oigodesk inboxes.

€ Payment eventsoigoecomm: payment status via a signed Stripe webhook.

⚭ Cross-productoigohotel ↔ oigodesk: customer matching and tickets by hotel ID.

Custom API

We build the endpoint you need.

When the existing API isn't enough, or your own system needs one, we deliver to these standards:

{ }

REST or GraphQL

REST or GraphQL as needed; JSON responses, consistent error codes and pagination.

▤

Documentation

An OpenAPI (Swagger) spec, example requests and change notes.

⚗

Test environment

A sandbox with separate keys to try everything before going live.

⛨

Security

API keys or OAuth, permission scopes, rate limiting and access logs.

↻

Outgoing webhooks

Event notifications to your system; signed requests and retries on failure.

Versioning

Endpoints are versioned, so updates don't break your existing integrations.

Process

How to get API access.

It starts with a short call.

Request

Tell us which product you want to connect to, and why.

API key

We create a key for your company and share the endpoints and examples.

Build & test

Our team answers your questions while you build the integration.

Live & support

After launch we announce changes in advance and keep versions stable.

FAQ

Common questions about the API.

Technical question? Write to our team.

Which products have an API?

oigodesk has a REST API for tickets and comments, a live chat API and email-to-ticket. oigohotel and oigoecomm receive channel manager, WhatsApp, Instagram and payment events via webhooks. For other products we open the endpoints your project needs.

How does authentication work?

Requests are authenticated with a company-specific API key sent in the Authorization: Bearer header. Each key only reaches its own company's data.

How do I get an API key?

Tell us which product you want to connect to and why; we create a key for your company and send it with the endpoint list and examples.

Do you build APIs for our own system?

Yes. REST or GraphQL APIs, delivered with OpenAPI documentation, a test environment, versioning and outgoing webhooks.

Are there rate limits?

Yes; public endpoints (such as live chat) are rate limited. For high-volume use we tune the limits to your needs.

Let's connect via API.

Tell us what you want to connect; we'll send your key and docs, or quote the API you need.

Request API access → contact@oigoworks.com