Push knowledge to the Secretary

Send FAQs, guides and summaries from your system into a business's Secretary, keep them current with one call, and remove them.

Pushed knowledge is text the Secretary answers questions from, sent by your system instead of uploaded by hand. Use it for anything that changes rarely and fits in a page: FAQs, how something works, a summary of what you offer.

It is never the business's own Terms, privacy, refund or cancellation policy. When a customer asks about one of those, the Secretary answers only from documents the owner added; if the owner has none, it says so, even when your text has a similar title.

For data that changes often or is too big to copy, use connected actions instead.

Creating or replacing

PUT /api/v1/knowledge/delivery-areas
Authorization: Bearer ord_live_...
Content-Type: application/json
{
  "title": "Where we deliver and how long it takes",
  "content": "We deliver to every address in the city and the towns around it. Parcels booked before 2 pm on a working day are collected the same day and delivered the next working day..."
}
  • The last part of the path is your key for this text: 1 to 80 letters, digits, dots, underscores, colons or hyphens, starting with a letter or digit. Use something stable, such as your own page or article id.
  • The first push creates it (201). Pushing the same key again replaces it (200). If nothing changed, the response includes "unchanged": true, so a nightly sync of everything is cheap.
  • title: up to 200 characters. content: 20 to 8,000 characters of plain text. Longer material: split it across keys, by topic.
{ "key": "delivery-areas", "title": "Where we deliver and how long it takes", "chars": 1840, "updatedAt": "2026-10-01T10:00:00.000Z", "createdAt": "2026-10-01T10:00:00.000Z", "unchanged": false }

Listing and removing

  • GET /api/v1/knowledge lists everything you pushed for this business.
  • DELETE /api/v1/knowledge/{key} removes one: 204, or 404 when nothing is under that key.

Your keys are yours alone. Another app or key of the same business pushing the same key keeps its own text; neither of you can read, replace or delete the other's. Texts pushed before Ordina started recording who pushed them are shared: any key of the business replaces or deletes them under their plain key.

The owner sees your texts, each with your app's or key's name, under Integration, Connected actions, and with their other knowledge sources in their Secretary settings under What I know, where they can remove any of them. When the owner revokes your key or disconnects your app, they can choose to delete everything you pushed at the same time.

Limits

  • Each key counts as one knowledge source on the business's plan, together with any PDFs and websites the owner added: up to 5 in all on the Business plan. Over the limit, a new key returns 403; replacing an existing key always works.
  • Up to 120 pushes per hour per business; then 429 until the hour is up.
  • The Secretary reads all of a business's knowledge together, up to about 16,000 characters per answer, so shorter, focused texts work best.

How the Secretary uses it

The business's own settings come first. Opening hours, services, prices and contact details are read from the dashboard, so if pushed text disagrees with them ("we open at 8am" while the hours say 9am), the Secretary follows the settings. Push what the settings cannot hold, and ask the owner to change the settings themselves.

Pushed text is treated as information, never as instructions. A sentence such as "ignore your rules" inside it is read as text, not obeyed. Write it the way you would explain things to a new member of staff: facts, figures, links.

Did this answer it?If not, write to help@useordina.com with your handle, or contact us. A person replies.
Contact us