POST Requests

In the event of processing larger numbers of variants, please switch to using the POST message type encoded in JSON format.

For the VEP endpoints

Set your accepts header to application/json Set your content-type to one of those available The message body consists of a key (ids or variants) depending on the endpoint followed by a list of values.

[/vep/:species/region] accepts variants in all the VEP-supported formats, with one line of the original file comprising one element of the list. Examples of these formats can be found in the Ensembl VEP help page VEP options (hgvs, maf_1kg etc.) can be specified as additional keys in the message body as well as URL parameters. batch your requests by up to one thousand per POST and wait patiently. This is a shared resource, and excessive requests will not increase performance but will impact other users.

For the Archive endpoint

In the event of using the archive endpoint heavily, consider switching to POST messages containing batches of IDs.

Set your accepts header to application/json Set your content-type to application/json The message body consists of the key "id" followed by a list of IDs. Archive lookups are not as fast as the VEP, please limit your requests to 400 IDs per batch for decent performance and respectful usage.