Retrieve a Provider's Instruction Override
Returns the custom connection instructions stored for one provider — the focused read an editor loads before saving.
404. Use Retrieve a Provider Overlay, which never 404s, when you want the overlay whether or not an override exists.
null, not an empty list. Absent means “keep the Yuno catalogue’s value”; present-and-empty means “replace it with nothing”.Path Parameters
Response
step, text, text_link, link, type, has_sub_instructions, sub_instructions_type and sub_instructions (nested up to 3 levels). text and text_link are either a plain string or a language map such as {"EN": "...", "ES": "..."}.title, order, instructions_type and instructions (the same step shape).created_by.Errors
Authorizations
Path Parameters
Yuno catalogue provider id in UPPER_SNAKE_CASE. Case-insensitive; normalized to upper case.
"STRIPE"
Response
The stored override.
Yuno catalogue provider id, UPPER_SNAKE_CASE.
"STRIPE"
Connection steps replacing the catalogue's.
Grouped setup steps replacing the catalogue's.
Documentation link replacing the catalogue's, when overridden. Always https.
"https://docs.example.com/stripe"
Display name replacing the catalogue's, when overridden. Only Yuno-owned providers can carry one.
"Acme Risk"
When the override was first written.
"2026-09-02T13:54:13Z"
When the override was last written.
"2026-09-02T13:54:13Z"
The dashboard user who created it. Overrides written through this API carry the all-zero sentinel 00000000-0000-0000-0000-000000000000, meaning "written through the API" rather than by a person in the dashboard.
"00000000-0000-0000-0000-000000000000"
The dashboard user who last updated it, with the same sentinel rule as created_by.
"00000000-0000-0000-0000-000000000000"