---
title: "Declared-origin taxonomy for the Adicionar Lead selector"
method: GET
path: "/api/leads/origins"
tags: ["Leads - Admin"]
---

# Declared-origin taxonomy for the Adicionar Lead selector

`GET /api/leads/origins`

Options for the manual "Origem da lead" selector (ticket #726).

Served from the backend so the frontend cannot drift from the keys actually
persisted in Z_Leads.declared_origin — the mistake SOURCE_OPTIONS /
REQUEST_SOURCE_LABELS already made in call-tracking, where two hand-synced
copies of the same list live in two repos.

The list is GLOBAL, not tenant-scoped: a declared "standvirtual" has to be
the same key for every company or it stops being comparable to the measured
one. Hence no idcompany here — there is no tenant data to leak. Auth still
applies (protected_router is gated globally).

## Headers

- `x-api-token` string, nullable

## Response `200`

Successful Response

- unknown

## Other responses

- `422` — Validation Error

---

[API](https://skmtc.dev/multigest/apis/multigest-protected-api.md) · [All operations](https://skmtc.dev/multigest/apis/multigest-protected-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/multigest/multigest-protected-api/revisions/4b44eb76b3ee/schema)