For the complete documentation index, see llms.txt. This page is also available as Markdown.

Suspected fraud query

The suspected fraud query retrives the suspected frauds by a conditional search.

Suspected Fraud Query

post
Authorizations
AuthorizationstringRequired

JWT Authorization header using the Bearer scheme.

Body
queryModestring · enumOptionalPossible values:
pageintegerOptional

The page number to request in paginated queries.

startDatestring · date-timeOptional

The start Date Time of consult, ISO 8621 format.

endDatestring · date-timeOptional

The end Date Time of consult, ISO 8621 format.

Responses
200

Suspected fraud query occurred successfully.

application/json
messagestringRequired

Human readable message informing about the operation.

amountintegerRequired

Total amount of query results.

totalPagesintegerOptional

The total number of pages in a paginated response.

Example: 2
currentPageintegerOptional

The current page in a paginated response.

post/query

Options

As demonstrated in the example request you can set the above properties to the search/query the suspected frauds:

  • The identifier object is used to query suspected fraud occurrences, is composed by data (a string representing the document number) and by type (must be CPF or CNPJ). It's a required property;

  • The queryMode property indicates how the query is be performed, it's an optional field and your default value is DEFAULT. The possible values are:

    • DEFAULT: It's the conventional mode, propagates the query to All.Id Network and to all available hubs of the consortium network;

    • LOCAL: Indicates that the query will be executed locally on the Peer, without propagating the query to the network. A unique identifier per SuspectedFraud is returned, a UUID named token;

    • INTERNAL: Indicates that the query will be executed internally in the All.Id Network, not propagating to the consortium network;

    • DELETED: Similar to LOCAL mode, the query will be executed locally but returning SuspectedFraud's marked as deleted.

  • The startDate and endDate properties must be strings representing a date-time ISO format. Those properties must be optional.

  • The page property should only be used for queries with paginated responses due to the excessive size of the data. It is an optional integer field. If not specified, a standard query is executed; if specified, it retrieves the requested page.

Paginated Responses

Paginated responses are used to handle the large volume of aggregated data returned. Each page contains up to 5,000 entries and is ordered by occurrence date, with the most recent entries appearing first.

Pages are valid for 1 hour. After this period, any attempt to access these pages will result in an error. Similarly, attempting to retrieve pages for non-paginated queries will also result in an error.

Pagination uses 0-based indexing — ensure this is followed when requesting subsequent pages.

Last updated