Support

Stuck, found a bug, or need a limit raised? Write to us.

Contact

E-mail support@officehero.io.

Ask us for:

• personal-data (PII) events on a webhook endpoint — include the endpoint id and why it needs the data;
• an API key with int:*, which webhook subscriptions to compliance, e-invoicing, DATEV, tachograph, dashcam and e-signature events need and which Settings → API keys does not offer — the same goes for int:messaging.messages:read and int:identity.users:read, the scopes of the messaging and identity events;
• more than five webhook endpoints, or a higher rate limit;
• a data processing agreement;
• access to the MCP server or OAuth app registration.

What to include

• The x-trace-id response header, when you have one.
• The time of the request in UTC, the method and the path.
• The status and the problem document's detail_key.
• Your API key's prefix (the 12 characters after oh_live_) — never the full key.
• For webhooks: the endpoint id and the event id (evt_…).

Terms and data protection

Use of the API is governed by the OfficeHero terms and conditions. Data you read through the API is your company's data, processed as our privacy policy describes. For a data processing agreement, write to support@officehero.io.