Re-map a custom API source's stored records
Start a remap job (kind remap): it re-maps the stored provider record of every finding of the source under the current mapping, without fetching anything. It updates the finding columns, content hash and revision as a synchronization would, recomputes the source’s coverage and applies the usual needs_attention or ready transition. Findings without a stored record stay as they are, and a finding’s external key never changes. Team admins only. While a synchronization or another remap of the source is queued or running, the request is refused with 409 sync_in_progress.
Authorizations
JWT authentication token
Headers
Optional key that makes a repeated request return the same job instead of starting another one. Without it, Neo derives a key from the source's configuration (a new manual synchronization gets a new key).
1 - 200Path Parameters
Source id

