HERE GNSS Data API v2

{"openapi":"3.0.2","info":{"title":"HERE GNSS Data API v2","version":"2.2.1","description":"GNSS Data API v2 is a service for accessing GNSS data.\nIt provides Assisted GNSS (A-GNSS) data and navigation model predictions\nfor GPS, GLONASS, Galileo, BeiDou and QZSS satellite systems\nto improve the performance of GNSS receivers.\n\nThis API returns responses in the LPP ASN.1 format, encoded using Encoding\nRules as specified by the\n[3GPP and ETSI standards](https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=3710).\n","contact":{},"termsOfService":"https://legal.here.com/en-gb/terms/here-platform","license":{"name":"HERE Documentation License","url":"https://legal.here.com/en-gb/terms/documentation-license","x-copyright":"Copyright (C) 2026 HERE Europe B.V."}},"servers":[{"url":"https://gnss.hereapi.com/v2","description":"Production Server"}],"security":[{"ApiKey":[]},{"Bearer":[]}],"paths":{"/assistance":{"get":{"description":"Request real-time A-GNSS data for GPS, GLONASS, Galileo, BeiDou, or QZSS satellite systems.\n\nThis service provides following GNSS Assistance Data Elements,\nsee [3GPP TS 37.355 specification](https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=3710)\nfor detailed information.\n\n- GNSS-ReferenceTime\n- GNSS-IonosphericModel\n- GNSS-TimeModelList\n- GNSS-NavigationModel\n- GNSS-RealTimeIntegrity\n- GNSS-Almanac\n- GNSS-UTC-Model\n- GNSS-AuxiliaryInformation\n\n**Note**, these values are based on the current service configuration and may be changed in future.\nAvailability of the above data elements depend on the GNSS system.\n\nGNSS assistance data is typically updated every 30 - 60 minutes depending on the GNSS system.\n","summary":"Real-time assistance data","operationId":"HERE GNSS Data API v2 getAssistance","tags":["GNSS Data"],"parameters":[{"$ref":"#/components/parameters/GnssAssistance"},{"$ref":"#/components/parameters/LppEncodingAssistance"},{"$ref":"#/components/parameters/LppRoot"},{"$ref":"#/components/parameters/BillingTag"},{"$ref":"#/components/parameters/AcceptForEncoding"},{"$ref":"#/components/parameters/AcceptEncodingForLppData"},{"$ref":"#/components/parameters/RequestID"}],"responses":{"200":{"$ref":"#/components/responses/SuccessAssistance"},"400":{"$ref":"#/components/responses/Error400"},"401":{"$ref":"#/components/responses/Error401"},"403":{"$ref":"#/components/responses/Error403"},"429":{"$ref":"#/components/responses/Error429"},"default":{"$ref":"#/components/responses/ErrorDefault"}}}},"/prediction":{"get":{"description":"Request predicted GNSS navigation models for GPS, GLONASS, Galileo, or BeiDou satellite systems.\n\nThis service provides predicted navigation models for a certain amount of upcoming days in a\nseries of LPP messages, each of which covers a specific time interval, as shown in the table below:\n\n| GNSS    | Message validity | Total prediction |\n| ------- | ---------------  | ---------------- |\n| GPS     | 4 hours          | up to 14 days    |\n| GLONASS | 30 minutes       | up to 14 days    |\n| Galileo | 4 hours          | up to 7 days     |\n| BeiDou  | 4 hours          | up to 7 days     |\n\n**Note**, these values are based on the current service configuration and may be changed\nin future. The validity period of each LPP message is provided in the response, so clients\nshould rely on that information instead of the values in the table above.\n\nThe service returns prediction data for up to 48 hours per request.\nClient specifies required GNSS system(s) and the start time for the prediction data\nby query parameters 'gps', 'glo', 'gal' and 'bds' for GPS, GLONASS, Galileo and BeiDou\nsystems, respectively.\n\nTo get the first 48 hours of prediction data for a specific GNSS system,\nthe client can set the corresponding parameter to `now`, or to the current time as Unix time\nor GNSS time in seconds. The first LPP message for the corresponding GNSS system\nin the response will have a validity interval that covers this start time,\nand the following LPP messages will have consecutive validity intervals that together\ncover up to 48 hours of prediction data.\n\nEach LPP message in the response contains predicted navigation models for just one GNSS system.\nEach body part in multipart responses corresponds to a single LPP message for a specific\nGNSS system and is described with following headers:\n  - `X-Constellation` indicating the GNSS system of the message,\n     with values `gps`, `glo`, `gal` or `bds` for GPS, GLONASS, Galileo and BeiDou systems,\n     respectively\n  - `X-Validity-Start` indicating the validity start time in seconds since Unix epoch\n  - `X-GNSS-Validity-Start` indicating the validity start time in seconds since\n     corresponding GNSS epoch\n  - `X-Validity-Duration` indicating the validity duration in seconds\n\nJSON responses contain the same validity information in the `validity` field with each LPP message.\n\nTo get prediction data for next 48-hour intervals, send follow-up requests.\nIn order to avoid receiving duplicate LPP messages, set each time parameter\nto the validity end time of the last received LPP message for the corresponding GNSS system.\nThe validity end time can be calculated as the sum of the validity start time and\nthe validity duration.  For simplicity of client implementation, the service sends\nthe query string with properly set time parameters for the next request for prediction data\nin the `X-Prediction-Next` response header.\n\nFor example, suppose the initial client's request is `GET /v2/prediction?gps=now&glo=now`.\nThe response contains prediction data for GPS and GLONASS systems,\nand the last LPP message for GPS has validity\nstart time 1772380800 and validity duration 14400, while the last LPP message\nfor GLONASS has validity start time 1772393400 and validity duration 1800.\nThe response also contains header `X-Prediction-Next: gps=1772395200&glo=1772395200`.\nThe client can calculate new time parameters for each constellation by adding the validity\nstart times and durations, or simply use the value of `X-Prediction-Next` header,\nto build the next request URL: `GET /v2/prediction?gps=1772395200&glo=1772395200`.\n(This example uses Unix times, but the same logic applies if the client uses GNSS times.\nBoth the initial and the next request URLs might need additional parameters,\nsuch as `lpp` or `apiKey`.)\n\nRepeating this process, the client can get prediction data for the full 14-day period\nfor GPS and GLONASS systems in 7 requests, and for the full 7-day period for\nGalileo and BeiDou systems in 4 requests.\n","summary":"Predicted GNSS navigation models","operationId":"HERE GNSS Data API v2 getPrediction","tags":["GNSS Data"],"parameters":[{"$ref":"#/components/parameters/GpsStart"},{"$ref":"#/components/parameters/GlonassStart"},{"$ref":"#/components/parameters/GalileoStart"},{"$ref":"#/components/parameters/BeidouStart"},{"$ref":"#/components/parameters/LppEncodingPrediction"},{"$ref":"#/components/parameters/LppRoot"},{"$ref":"#/components/parameters/BillingTag"},{"$ref":"#/components/parameters/AcceptForEncoding"},{"$ref":"#/components/parameters/AcceptEncodingForLppData"},{"$ref":"#/components/parameters/RequestID"}],"responses":{"200":{"$ref":"#/components/responses/SuccessPrediction"},"400":{"$ref":"#/components/responses/Error400"},"401":{"$ref":"#/components/responses/Error401"},"403":{"$ref":"#/components/responses/Error403"},"406":{"$ref":"#/components/responses/Error406"},"429":{"$ref":"#/components/responses/Error429"},"default":{"$ref":"#/components/responses/ErrorDefault"}}}},"/health":{"get":{"summary":"Service health","description":"Tests basic health of the service","operationId":"HERE GNSS Data API v2 getHealth","tags":["API Information"],"parameters":[{"$ref":"#/components/parameters/RequestID"}],"responses":{"200":{"description":"Health status","headers":{"X-Request-ID":{"$ref":"#/components/headers/RequestID"},"X-Correlation-ID":{"$ref":"#/components/headers/CorrelationID"}},"content":{"application/json":{"schema":{"$ref":"#/components/schemas/HealthResponseOk"}}}},"401":{"$ref":"#/components/responses/Error401"},"default":{"description":"Health response in case of failure.","headers":{"X-Correlation-ID":{"$ref":"#/components/headers/CorrelationID"},"X-Request-ID":{"$ref":"#/components/headers/RequestID"}},"content":{"application/json":{"schema":{"$ref":"#/components/schemas/HealthResponseFail"}}}}}}},"/version":{"get":{"summary":"API version","description":"Retrieves API Specification version information","operationId":"HERE GNSS Data API v2 getApiVersion","tags":["API Information"],"parameters":[{"$ref":"#/components/parameters/RequestID"}],"responses":{"200":{"description":"Version of API","headers":{"X-Request-ID":{"$ref":"#/components/headers/RequestID"},"X-Correlation-ID":{"$ref":"#/components/headers/CorrelationID"}},"content":{"application/json":{"schema":{"$ref":"#/components/schemas/ApiVersion"}}}}}}},"/openapi":{"get":{"summary":"OpenAPI specification","description":"Retrieves OpenAPI specification of this API","operationId":"HERE GNSS Data API v2 getOpenApi","tags":["API Information"],"parameters":[{"$ref":"#/components/parameters/RequestID"},{"$ref":"#/components/parameters/AcceptOpenApi"},{"$ref":"#/components/parameters/AcceptEncoding"}],"responses":{"200":{"description":"API specification file is returned","headers":{"X-Request-ID":{"$ref":"#/components/headers/RequestID"},"X-Correlation-ID":{"$ref":"#/components/headers/CorrelationID"},"Content-Encoding":{"$ref":"#/components/headers/ContentEncoding"}},"content":{"application/json":{"schema":{"type":"object","description":"This specification as JSON object"},"example":{"openapi":"3.0.2","info":{"title":"HERE GNSS Data API v2"},"paths":{}}},"application/yaml":{"schema":{"type":"object","description":"This specification in YAML format"},"example":"openapi: 3.0.2\ninfo:\n  title: HERE GNSS Data API v2\npaths: {}\n"}}},"default":{"$ref":"#/components/responses/ErrorDefault"}}}}},"components":{"headers":{"AcceptEncoding":{"description":"Indicates supported content encodings in responses. Supported codings are: \"gzip\", \"deflate\", \"br\".\n","schema":{"type":"string"}},"ContentEncoding":{"description":"Indicates that the data in the body has been compressed. Supported codings are: \"gzip\", \"deflate\", \"br\".\n","schema":{"type":"string"},"example":"gzip"},"CorrelationID":{"description":"Auto-generated ID, which uniquely identifies the request.\nWhen contacting support with an inquiry regarding a specific request,\nprovide the value of this header which will help troubleshooting the issue.\n**Note:** its value is currently in UUID format, but this may be changed\nin future and relying upon this specific format is deprecated!\n","schema":{"type":"string"}},"RequestID":{"description":"Value of X-Request-ID header parameter supplied in the request.","schema":{"type":"string"}},"RetryAfter":{"description":"Number of seconds to wait before making a new request.","schema":{"type":"integer"}}},"parameters":{"AcceptEncoding":{"name":"Accept-Encoding","in":"header","description":"Indicates preferred content encodings in the response. The server uses content negotiation (see RFC 9110) to select the best option and informs the choice in the `Content-Encoding` response header. Supported encodings are: \"gzip\", \"deflate\", \"br\" (and \"identity\"). For any other value, or if this header is missing, the response will be uncompressed.\n","schema":{"type":"string"},"required":false,"example":"gzip;q=0.9, br;q=1"},"AcceptEncodingForLppData":{"name":"Accept-Encoding","in":"header","description":"Indicates preferred content encodings in the response. The server uses content negotiation (see RFC 9110) to select the best option and informs the choice in the `Content-Encoding` response header. Supported encodings are: \"gzip\", \"deflate\", \"br\" (and \"identity\"). If this header is missing, the response may or may not be compressed, client has to check the response headers for that information. If all supported encodings are disabled (e.g. \"*;q=0\"), the server will respond with status code 406 \"Not Acceptable\".\n","schema":{"type":"string"},"required":false,"example":"gzip;q=0.9, br;q=1"},"AcceptForEncoding":{"name":"Accept","description":"Indicates preferred media types for the response. The server uses content negotiation (see RFC 9110) to select the best option and informs the choice in the `Content-Type` response header. Note that the response content type also depends on `encoding` query parameter value. For example, if `encoding=uper`, and this header requests JSON response, the server will respond with status code 406 \"Not Acceptable\".\n","in":"header","required":false,"schema":{"type":"string"},"examples":{"json":{"summary":"Requesting JER-encoded LPP messages as single JSON object","value":"application/json"},"jsonlines":{"summary":"Requesting JER-encoded LPP messages as JSON texts sequences","value":"application/json-seq"}}},"AcceptOpenApi":{"name":"Accept","description":"Indicates preferred media types for the response. The server uses content negotiation (see RFC 9110) to select the best option and informs the choice in the `Content-Type` response header. Supported media types are `application/json` for JSON response and `application/yaml` for YAML response. (Deprecated YAML media types `application/x-yaml`, `text/yaml` and `text/x-yaml` are also supported.) If this header is missing or specifies any other media type, the response will be in JSON format.\n","in":"header","required":false,"schema":{"type":"string"},"example":"application/yaml;q=0.9, application/json;q=0.8"},"BillingTag":{"name":"billingTag","description":"A list of up to six billing tags, separated by the + sign. This parameter provides a way to track your platform usage. For details, refer to the Cost Management Developer Guide section on [Billing Tags](https://www.here.com/docs/bundle/cost-management-developer-guide/page/topics/tutorial-billing-tags.html).\n","in":"query","schema":{"type":"string","minLength":4,"maxLength":101},"example":"ABCD+EFGH"},"GnssAssistance":{"name":"gnss","description":"Specifies the GNSS system(s) for which real-time assistance data is requested.\nData for multiple GNSS systems can be requested by specifying several supported values\nseparated by comma.\n\nSupported values are:\n  - `gps`: Global Positioning System (GPS)\n  - `glo`: Global Navigation Satellite System (GLONASS)\n  - `gal`: Galileo Navigation Satellite System\n  - `bds`: BeiDou Navigation Satellite System\n  - `qzs`: Quasi-Zenith Satellite System (QZSS)\n\nIf this parameter is not provided, data for all supported GNSS systems is returned.\n","in":"query","required":false,"schema":{"type":"array","items":{"type":"string","enum":["gps","glo","gal","bds","qzs"]},"uniqueItems":true},"example":["gps","glo","bds"],"style":"form","explode":false},"LppEncodingAssistance":{"name":"encoding","description":"Specifies the encoding format for the LPP messages in the response.\nSupported values as per ASN.1 specification are:\n  - `jer`: JSON Encoding Rules (JER).\n    The response content type depends on `Accept` header and can be either of the following:\n       - `application/json-seq` (default) - JSON text sequences with each item containing a single LPP message in JER format.\n       - `application/json` - single JSON object, which contains one or more LPP messages in JER format.\n       - `application/x-ndjson` - newline-delimited JSON objects, each containing a single LPP message in JER format.\n  - `uper`: Unaligned Packed Encoding Rules (UPER).\n    The response content type is `multipart/mixed` and it consists of\n    one or more binary LPP messages in `application/octet-stream` format.\n","in":"query","required":false,"schema":{"type":"string","enum":["uper","jer"],"default":"uper"},"example":"jer"},"LppEncodingPrediction":{"name":"encoding","description":"Specifies the encoding format for the LPP messages in the response.\nSupported values as per ASN.1 specification are:\n  - `jer`: JSON Encoding Rules (JER).\n    The response content type depends on `Accept` header and can be either of the following:\n       - `application/json-seq` (default) - JSON text sequences with each item containing a single LPP message in JER format.\n       - `application/json` - single JSON object, which contains one or more LPP messages in JER format.\n       - `application/x-ndjson` - newline-delimited JSON objects, each containing a single LPP message in JER format.\n  - `uper`: Unaligned Packed Encoding Rules (UPER).\n    The response content type is `multipart/mixed` and it consists of\n    one or more binary LPP messages in `application/octet-stream` format.\n\nPrediction navigation models can be large, so UPER encoding is recommended for this endpoint\nto reduce the response size. If client requests JER encoding for prediction data,\nthe server always compresses the response (by default with \"gzip\" content encoding).\nIf the client disables all supported compression methods via `Accept-Encoding` header,\nthe server will respond with status code 406 \"Not Acceptable\".\n","in":"query","required":false,"schema":{"type":"string","enum":["uper","jer"],"default":"uper"},"example":"jer"},"LppRoot":{"name":"lpp","description":"Specifies the LPP ASN.1 element to be used as the root element for the LPP messages in the response.\nSupported values are:\n  - `data`: The root element is the `A-GNSS-ProvideAssistanceData` sequence.\n  - `full`: The root element is the `LPP-Message` sequence.\n\nClients might be able to reduce the size of the code used to parse ASN.1 messages\nby requesting `data` as the root element, especially for binary encodings, such as UPER.\n","in":"query","required":false,"schema":{"type":"string","enum":["data","full"],"default":"data"},"example":"full"},"GpsStart":{"name":"gps","description":"Requests predicted navigation models for GPS system starting from the specified time, as Unix time or GPS time, in seconds. The validity interval of the first LPP message in the response covers this start time. Validity intervals of all LPP messages are consecutive and together they cover up to 48-hour time interval.\n\nThe service only provides data within the range from current time up to the total GPS prediction period in the future. If this parameter defines a time interval outside this range, then no GPS prediction messages are included in the response. Special value `now` is used to request predictions starting from the current time.\n\nIf this parameter is not provided, the response does not include GPS predictions.\n","in":"query","required":false,"schema":{"oneOf":[{"type":"integer","minimum":0},{"type":"string","enum":["now"]}]},"examples":{"unixTimestamp":{"summary":"Request data using Unix time in seconds","value":1772380800},"gnssTimestamp":{"summary":"Request data using GPS time in seconds","value":1456416018},"now":{"summary":"Request data from current time","value":"now"}}},"GlonassStart":{"name":"glo","description":"Requests predicted navigation models for GLONASS system starting from the specified time, as Unix time or GLONASS time, in seconds. The validity interval of the first LPP message in the response covers this start time. Validity intervals of all LPP messages are consecutive and together they cover up to 48-hour time interval.\n\nThe service only provides data within the range from current time up to the total GLONASS prediction period in the future. If this parameter defines a time interval outside this range, then no GLONASS prediction messages are included in the response. Special value `now` is used to request predictions starting from the current time.\n\nIf this parameter is not provided, the response does not include GLONASS predictions.\n","in":"query","required":false,"schema":{"oneOf":[{"type":"integer","minimum":0},{"type":"string","enum":["now"]}]},"examples":{"unixTimestamp":{"summary":"Request data using Unix time in seconds","value":1772380800},"gnssTimestamp":{"summary":"Request data using GLONASS time in seconds","value":951937200},"now":{"summary":"Request data from current time","value":"now"}}},"GalileoStart":{"name":"gal","description":"Requests predicted navigation models for Galileo system starting from the specified time, as Unix time or Galileo time, in seconds. The validity interval of the first LPP message in the response covers this start time. Validity intervals of all LPP messages are consecutive and together they cover up to 48-hour time interval.\n\nThe service only provides data within the range from current time up to the total Galileo prediction period in the future. If this parameter defines a time interval outside this range, then no Galileo prediction messages are included in the response. Special value `now` is used to request predictions starting from the current time.\n\nIf this parameter is not provided, the response does not include Galileo predictions.\n","in":"query","required":false,"schema":{"oneOf":[{"type":"integer","minimum":0},{"type":"string","enum":["now"]}]},"examples":{"unixTimestamp":{"summary":"Request data using Unix time in seconds","value":1772380800},"gnssTimestamp":{"summary":"Request data using Galileo time in seconds","value":837100818},"now":{"summary":"Request data from current time","value":"now"}}},"BeidouStart":{"name":"bds","description":"Requests predicted navigation models for BeiDou system starting from the specified time, as Unix time or BeiDou time, in seconds. The validity interval of the first LPP message in the response covers this start time. Validity intervals of all LPP messages are consecutive and together they cover up to 48-hour time interval.\n\nThe service only provides data within the range from current time up to the total BeiDou prediction period in the future. If this parameter defines a time interval outside this range, then no BeiDou prediction messages are included in the response. Special value `now` is used to request predictions starting from the current time.\n\nIf this parameter is not provided, the response does not include BeiDou predictions.\n","in":"query","required":false,"schema":{"oneOf":[{"type":"integer","minimum":0},{"type":"string","enum":["now"]}]},"examples":{"unixTimestamp":{"summary":"Request data using Unix time in seconds","value":1772380800},"gnssTimestamp":{"summary":"Request data using BeiDou time in seconds","value":636307204},"now":{"summary":"Request data from current time","value":"now"}}},"RequestID":{"name":"X-Request-ID","description":"User-provided token that can be used to trace a request or a group of requests sent to the service. Can be any string, but UUID is recommended. It will be echoed in the response.\n","in":"header","required":false,"schema":{"type":"string"}}},"responses":{"Error400":{"description":"Bad request. The request is malformed - the URL query parameters in the request are invalid. Check the message in the response for additional troubleshooting information.\n","headers":{"X-Request-ID":{"$ref":"#/components/headers/RequestID"},"X-Correlation-ID":{"$ref":"#/components/headers/CorrelationID"}},"content":{"application/json":{"schema":{"$ref":"#/components/schemas/Error"},"example":{"title":"Bad Request","status":400,"code":"E619400","cause":"Query parameter validation error","action":"Please correct the request and retry","correlationId":"4199533b-6290-41db-8d79-e2bef401749a","details":[{"title":"Violated rule: supportedGnss","message":"GNSS should be one of 'gps, glo, gal, bds'"}]}}}},"Error401":{"description":"Authentication failed.","headers":{"X-Request-ID":{"$ref":"#/components/headers/RequestID"},"X-Correlation-ID":{"$ref":"#/components/headers/CorrelationID"}},"content":{"application/json":{"schema":{"$ref":"#/components/schemas/AuthError"},"example":{"error":"Unauthorized","error_description":"Token Validation Failure - invalid time in token"}}}},"Error403":{"description":"Access denied.","headers":{"X-Request-ID":{"$ref":"#/components/headers/RequestID"},"X-Correlation-ID":{"$ref":"#/components/headers/CorrelationID"}},"content":{"application/json":{"schema":{"$ref":"#/components/schemas/AuthError"},"example":{"error":"Forbidden","error_description":"These credentials do not authorize access. Please contact your customer representative or submit a request here https://developer.here.com/contact-us to upgrade your account."}}}},"Error406":{"description":"Not Acceptable.","headers":{"X-Request-ID":{"$ref":"#/components/headers/RequestID"},"X-Correlation-ID":{"$ref":"#/components/headers/CorrelationID"},"Accept-Encoding":{"$ref":"#/components/headers/AcceptEncoding"}},"content":{"application/json":{"schema":{"$ref":"#/components/schemas/Error"},"example":{"title":"Not Acceptable","status":406,"code":"E619406","cause":"Content encoding not acceptable","action":"Please check the Accept-Encoding header in the request and retry with supported encoding.","correlationId":"4199533b-6290-41db-8d79-e2bef401749a"}}}},"Error429":{"description":"Too many requests in a given amount of time (rate limiting).","headers":{"X-Request-ID":{"$ref":"#/components/headers/RequestID"},"X-Correlation-ID":{"$ref":"#/components/headers/CorrelationID"},"Retry-After":{"$ref":"#/components/headers/RetryAfter"}},"content":{"application/json":{"schema":{"$ref":"#/components/schemas/AuthError"},"example":{"error":"Too Many Requests","error_description":"Rate limit for this service has been reached"}}}},"ErrorDefault":{"description":"Other possible errors","headers":{"X-Request-ID":{"$ref":"#/components/headers/RequestID"},"X-Correlation-ID":{"$ref":"#/components/headers/CorrelationID"}},"content":{"application/json":{"schema":{"$ref":"#/components/schemas/Error"},"examples":{"500 Internal Server Error":{"value":{"title":"Internal Server Error","status":500,"code":"E619500","cause":"Something unexpected happened.","action":"System administrators have been notified about the problem. Please try again later.","correlationId":"4199533b-6290-41db-8d79-e2bef401749a"}},"503 Service Unavailable":{"value":{"title":"Service Unavailable","status":503,"code":"E619503","cause":"The service is currently unavailable","action":"Please try again later","correlationId":"4199533b-6290-41db-8d79-e2bef401749a"}}}}}},"SuccessAssistance":{"description":"Request processed successfully and GNSS data included in the response. In case of If-Modified-Since header in the request, the response may contain only the parts of the data that have been modified since the specified date.\n","headers":{"X-Request-ID":{"$ref":"#/components/headers/RequestID"},"X-Correlation-ID":{"$ref":"#/components/headers/CorrelationID"}},"content":{"multipart/mixed":{"schema":{"type":"string","format":"binary","description":"The response body is one or more MIME multipart body parts, each of which is a single LPP message in requested encoding as per `encoding` query parameter. There will be exactly one part per requested GNSS system.\nIf assistance data for only some of requested GNSS systems cannot be provided, the corresponding part body contains a LPP message, whose `A-GNSS-ProvideAssistanceData` section includes only the `gnss-Error` field with corresponding `locationServerErrorCauses.cause` value. For example, should the data be temporarily not available on the server the cause will be set to `undeliveredAssistanceDataIsSupportedButCurrentlyNotAvailableByServer`.\nEach part is described with additional headers:\n  - `X-Constellation` (string) - GNSS system this LPP message contains data for.\n    Possible values are the same as for `gnss` query parameter.\n  - `X-GNSS-Error` (string, optional) - Included if assistance data for this GNSS\nsystem cannot be provided. Some of the values are (more may be added in future):\n      - \"currentlyNotAvailable\"\n"},"examples":{"success":{"$ref":"#/components/examples/MultipartSuccess"},"partialUnavailable":{"$ref":"#/components/examples/MultipartPartiallyUnavailable"}}},"application/json":{"schema":{"$ref":"#/components/schemas/AssistanceJsonBody"},"examples":{"success":{"$ref":"#/components/examples/JsonSuccessShort"},"failure":{"$ref":"#/components/examples/JsonPartiallyUnavailable"},"success-full":{"$ref":"#/components/examples/JsonSuccessFull"}}},"application/x-ndjson":{"schema":{"type":"string","description":"The response body is one or more newline-delimited JSON objects, each of which is JSON object in one of sub-schemas of `JsonMessage` schema. There will be exactly one JSON object in `AssistanceJsonMessage` sub-schema (i.e. `JsonSchema` with `type:\"assistance\"` property) per requested GNSS system. There may be other JSON objects with different `type` property values in the response as well, and clients should ignore objects with unrecognized `type` values. For example:\n```\n  Content-Type: application/x-ndjson\n\n  {\"type\":\"...\", ...}\n  {\"type\":\"assistance\",\"gnss\":\"gps\",\"lpp\":{...}}\n  {\"type\":\"assistance\",\"gnss\":\"glo\",\"lpp\":{...}}\n```\n","example":"{JSON 1}\n{JSON 2}\n..."}},"application/json-seq":{"schema":{"type":"string","description":"The response body is one or more JSON text sequences (as per RFC 7464), each of which is JSON object in one of sub-schemas of `JsonMessage` schema. There will be exactly one JSON object in `AssistanceJsonMessage` sub-schema (i.e. `JsonSchema` with `type:\"assistance\"` property) per requested GNSS system. There may be other JSON objects with different `type` property values in the response as well, and clients should ignore objects with unrecognized `type` values. For example:\n```\n  Content-Type: application/json-seq\n\n  \\x1E{\"type\":\"...\", ...}\n  \\x1E{\"type\":\"assistance\",\"gnss\":\"gps\",\"lpp\":{...}}\n  \\x1E{\"type\":\"assistance\",\"gnss\":\"glo\",\"lpp\":{...}}\n```\n","example":"\u001e{JSON 1}\n\u001e{JSON 2}\n..."}}}},"SuccessPrediction":{"description":"Request processed successfully and GNSS data included in the response. In case of If-Modified-Since header in the request, the response may contain only the parts of the data that have been modified since the specified date.\n","headers":{"X-Request-ID":{"$ref":"#/components/headers/RequestID"},"X-Correlation-ID":{"$ref":"#/components/headers/CorrelationID"},"X-Prediction-Next":{"description":"Time parameters to request the next batch of prediction data. This string includes updated time parameters (`gps`, `glo`, `gal`, `bds`) for each GNSS system listed in the request that has more prediction data available. Time values are in seconds since same epoch as in the request (Unix time or corresponding GNSS time). This header is omitted if there is no more prediction data available for any of the listed GNSS systems.\n","schema":{"type":"string"},"example":"gps=1772380800&glo=1772380800"}},"content":{"multipart/mixed":{"schema":{"type":"string","description":"The response body is one or more MIME multipart body parts, each of which is a single LPP message in requested encoding as per `encoding` query parameter. There may be several parts per each requested GNSS system, depending on how many LPP messages are required to cover for the whole requested prediction period.\n\nIf prediction data for only some of requested GNSS systems cannot be provided, the corresponding part body contains a LPP message, whose `A-GNSS-ProvideAssistanceData` section includes only the `gnss-Error` field with corresponding `locationServerErrorCauses.cause` value. For example, should the data be temporarily not available on the server the cause will be set to `undeliveredAssistanceDataIsSupportedButCurrentlyNotAvailableByServer`.\n\nEach part is described with additional headers:\n  - `X-Constellation` (string) - GNSS system this LPP message contains data for.\n    Possible values are `gps`, `glo`, `gal` and `bds` for GPS, GLONASS, Galileo\n    and BeiDou systems, respectively.\n  - `X-Validity-Start` (integer, optional) - Start time of the validity period\n    for this LPP message, in seconds since Unix epoch.\n    Omitted if prediction data for this GNSS system is not available.\n  - `X-Validity-Duration` (integer, optional) - Validity period duration\n    for this LPP message, in seconds.\n    Omitted if prediction data for this GNSS system is not available.\n  - `X-GNSS-Validity-Start` (integer, optional) - Start time of the validity period\n    for this LPP message, in seconds since corresponding GNSS epoch.\n    Note that the reference time value in the LPP message (`gnss-ReferenceTime` field)\n    corresponds to the middle of the validity period,\n    i.e. `X-GNSS-Validity-Start + (X-Validity-Duration / 2)`.\n    Omit

# --- truncated at 32 KB (49 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/here/refs/heads/main/openapi/here-gnss-data-v2-openapi.yml