TEteaflask
authed

Approve a suggested app page

Approves a suggested app page: a create adds it to the app pages, an update changes its page and a deprecation archives it, after the page passes the same checks. Approval is refused when the suggestion changed since you read its payload_fingerprint (read it again), and a create that conflicts with an existing page stays open.

post/api/v1/org-sitemap/proposals/{proposal_id}/approve

Request

  • Base URL
    https://api.teaflask.com (the document declares no server; this is the origin it was published from)
  • URL
    https://api.teaflask.com/api/v1/org-sitemap/proposals/{proposal_id}/approve
  • Auth
    none declared

Path parameters

proposal_idstring uuid required

The suggested app page's id, as list_org_sitemap_page_proposals returns it.

Request body

reviewed_fingerprintstring required

The payload_fingerprint of the suggestion as you read it; approval is consent to exactly that version.

Response

Successful Response

idstring uuid required
organization_idstring uuid required
kind'create' | 'update' | 'deprecate' required
page_idstring uuid nullable required
payloadobject required
payload_fingerprintstring required
status'open' | 'approved' | 'dismissed' | 'withdrawn' required
reviewed_by_user_idstring uuid nullable required
reviewed_atstring date-time nullable required
withdrawn_reasonstring nullable required
edited_by_user_idstring uuid nullable required
edited_atstring date-time nullable required
created_atstring date-time required
updated_atstring date-time required

Changes

No recorded changes to this operation across all 1 revision of this API.