How do I authenticate with the Just Eat UK API?

Most Just Eat endpoints require no bearer token of their own, so restaurant search, menu retrieval, and order placement are open, while partner operations use a bearer token in the Authorization header. You store any token once in your Jentic One instance, which supplies it on the calls that need it rather than exposing it to the agent.

Which endpoints are open and which need a token?

Discovery and order-flow endpoints in this specification declare no security requirement, while a small set of partner endpoints carry a bearer token requirement. Check each operation's security in the spec to see whether a token applies before calling it.

Does the API document rate limits?

The OpenAPI specification does not state rate limits; throughput and partner access depend on your agreement with Just Eat. Confirm the limits for your integration with Just Eat before running high-volume order or menu operations.

Can I limit what my agent is allowed to do with the Just Eat UK API?

Yes. Jentic lets you allow only the operations your agent needs, for example restaurant search and menu retrieval while withholding order placement and cancellation. Your Jentic One instance enforces that boundary on every call and keeps any token outside the agent's context.