How your application digests job results

Preview

This feature is not subject to our service terms. Pre-GA features are available as is and might have limited support.

For an example of a job response, see Synthetic job response For a reference of the job resource, see Job Reference. See JobV2 for the full schema.

Tip

Your consumer should be tolerant and expect that not all fields are always present or populated.

Warning

Your data source SHOULD consume the payload only for a completed job.

As soon as a job has the status completed, it is safe to consume the payload.

• Identifiers: You can use the job ID to trace the results back to a pending job request and the record in the destination system.
• Event codes: A single job may perform more than one task. For example, it may try to append a phone number or URL, or it may verify if the prospect currently works at the target company. For each task, the Modigie Real-Time Engine will emit event codes to indicate the outcome. Your client can use the event codes to selectively and efficiently consume the returned payload. See Job types and Job events.
• Outputs: Refer to the documentation on outputs for details on interpreting the results. See Job outputs.