Perk Travel (BYOK)

Perk Travel (BYOK) — connector documentation

• MCP endpoint: https://byok-perk-travel.connectorbay.com/mcp
• REST API: POST https://byok-perk-travel.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-perk-travel.connectorbay.com/openapi.json
• Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
• Authentication: your own Perk Travel Perk API key, sent in the X-Upstream-Key header of every request (never stored, logged or cached)
• Health: https://byok-perk-travel.connectorbay.com/health · Tool schemas: https://byok-perk-travel.connectorbay.com/tools.json
• Publisher: Unify Dynamics LLC · connectorbay.com/byok-perk-travel · agent@connectorbay.com

What Perk Travel (BYOK) is for

Perk Travel (BYOK) lets an AI assistant read your own Perk Travel data through the Perk Travel API with a key you supply (Perk API key). Read-only: 7 tools (list_trips, get_trip, list_invoices, get_invoice, list_invoice_lines, list_invoice_profiles, list_cost_centers). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.travelperk.com, api.perk.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Perk Travel. Perk Travel and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

• "Which business trips were booked or changed this month?"
• "Show the details of trip 75"
• "Which Perk invoices are still unpaid?"
• "Show the totals and tax summary of invoice INV-01-987654"
• "What did flights cost the company in October 2026?"
• "Which invoice profiles does our Perk account have?"

What it does

• list_trips: List the company's business trips, newest modification first, with name, dates, status (booked or cancelled), start and end location and booker id.
• get_trip: Get one trip by id with local and UTC start and end times, status, locations with coordinates and IATA code, and the booker id.
• list_invoices: List invoices issued to the company with serial number, status, dates, currency and total. Only invoices issued since 1 January 2019 are returned.
• get_invoice: Get one invoice by serial number with profile, dates, billing period, currency, total, tax summary and the count of lines. Bank details are not returned.
• list_invoice_lines: List invoice lines (individual trip expenses such as flights, hotels, trains) with date, description, amounts, service type, trip, cost center and vendor. Traveler names and emails are left out.
• list_invoice_profiles: List the invoice profiles (legal entities that trips are invoiced to) with name, payment method type, billing period, currency and legal name.
• list_cost_centers: List the company's cost centers with id, name, cost object type and number of assigned users.

BYOK key

You bring your own Perk Travel Perk API key (https://developers.perk.com/docs/quickstart). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to api.travelperk.com, api.perk.com over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

• https://developers.perk.com/docs/quickstart (the API this connector calls, with a BYOK key)

Live from the Perk Travel API (api.travelperk.com, api.perk.com) with a BYOK key; documentation: https://developers.perk.com/docs/quickstart. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Perk Travel. Perk Travel and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Perk Travel account.

Built for: Worldwide. Languages: English.

Perk Travel (BYOK) — Privacy Policy

Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What Perk Travel (BYOK) is. Perk Travel (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Perk Travel data: Read your company's Perk (TravelPerk) business trips, invoices, invoice lines, invoice profiles and cost centers with your own API key. You bring your own Perk Travel Perk API key; the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one Perk Travel call you asked for. Our application does not store it, write it to a log, put it in a cache, or share it. It is sent only to api.travelperk.com, api.perk.com, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If Perk Travel rejects it, we say so without repeating it.

What we receive. The arguments of each tool call, the BYOK key (for that call only), the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant) and standard server logs. What Perk Travel receives. The request we make on your behalf, including the key and the arguments, under Perk Travel's own terms and privacy policy. Perk Travel acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer Perk Travel gives for your request, trimmed to the fields the tool documents. We do not keep it: it is returned to your assistant and not stored, cached or used to train anything.

What we do not do. We do not build a profile, sell or share personal information, or keep your Perk Travel data. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting access logs (IP addresses, request paths and status codes) are kept for up to 30 days for security and abuse prevention; our application adds no request headers or bodies to them.

Sub-processors. Perk Travel (the API you call with a BYOK key, at your direction). Hosting: Vercel (United States regions).

Your rights. Because we store no personal data beyond short-lived logs, requests to access, correct or delete data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. Revoke your key at Perk Travel at any time to end all access.

Children. Perk Travel (BYOK) is a general-audience service operated by the adult using the assistant, under Perk Travel's own age rules.

Changes. We will post changes here with a new effective date.

Perk Travel (BYOK) — Terms of Service

Effective 24 October 2026. These terms govern use of the Perk Travel (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

1. The Service. Perk Travel (BYOK) provides: Read your company's Perk (TravelPerk) business trips, invoices, invoice lines, invoice profiles and cost centers with your own API key. It is accessed through an AI assistant or directly over MCP or HTTP, and is read-only.
2. Your own key, your own account. You must use your own Perk Travel credentials and only access data you are allowed to access. Perk Travel's terms apply to your use of Perk Travel; you are responsible for complying with them, including any rate limits and permitted uses. Do not share a key you do not own.
3. Independent. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Perk Travel. Perk Travel and its logos are trademarks of their owners and are used only to say which service the connector works with.
4. No advice, no guarantees. Output is the data Perk Travel returns, lightly trimmed; it may be incomplete, delayed or changed by Perk Travel. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your Perk Travel account.
6. Acceptable use. Automated use within the published rate limits is welcome. Do not use the Service to access data you are not entitled to, to circumvent Perk Travel's controls, or to attack any system.
7. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time; Perk Travel may change or end its API at any time.
8. Data. Our Privacy Policy describes what we process. In short: the BYOK key is used for the one call and not stored or logged.
9. Pro keys. Optional ConnectorBay Pro API keys are issued at our discretion and are separate from your Perk Travel key.
10. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service, including any action Perk Travel takes on your account. Our total liability is limited to US $100.
11. Governing law. California law; venue in San Mateo County, California.
12. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/byok-perk-travel

Perk Travel (BYOK) support

Email agent@connectorbay.com. We answer within two business days.

• MCP endpoint: https://byok-perk-travel.connectorbay.com/mcp
• REST API: https://byok-perk-travel.connectorbay.com/openapi.json
• Live status: https://byok-perk-travel.connectorbay.com/health

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. Perk Travel (BYOK) never asks for them.