Export Location Requests

List Export Location Requests

Open location-configuration requests for the caller's company, keyed by brand id so the Export tab can render "Aguarda configuração" in place of the request button.

Shape mirrors GET /integrazu/portal-config/status so the FE pattern is identical: {"2": {"ticket_id": 1234, "status": "open", "pv_id": 138, "requested_at": "2026-08-25T10:04:00"}}

JSON object keys are strings, so brand ids are stringified.

⚠️ pv_id NARROWS the tenant guard, it never replaces it (02-security.md §1) — idcompany always comes from the session.

⚠️ Non-critical by design: the FE swallows failures here and simply shows the request button. In particular, if the DDL has not been applied yet this endpoint fails while the Export tab itself keeps working, because get_brands_for_company() deliberately does not reference the new table.

get/api/integrazu/location-config/requests

Request

  • Base URL
    https://api.multigest.pt (the document declares no server; this is the origin it was published from)
  • URL
    https://api.multigest.pt/api/integrazu/location-config/requests
  • Auth
    API key in header x-api-token and API key in header x-origin-verify

Query parameters

pv_idinteger nullable

Narrow to one point of sale

Headers

x-api-tokenstring nullable

Response

Successful Response

unknown required

Changes

No recorded changes to this operation across all 21 revisions of this API.