RapidLEI Restful Web Services/APIs Collection
\n","schema":"https://schema.getpostman.com/json/collection/v2.0.0/collection.json","toc":[],"owner":"6519182","collectionId":"c30783bb-c64a-406a-b6e4-48d092570ea3","publishedId":"UVeFNSkp","public":true,"customColor":{"top-bar":"FFFFFF","right-sidebar":"303030","highlight":"EF5B25"},"publishDate":"2022-02-03T11:52:59.000Z"},"item":[{"name":"Production","item":[{"name":"General - API Health Check","id":"64c1ffac-5653-42bd-af09-0cd23800483a","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"GET","header":[],"url":"https://api.rapidlei.com/v1/health","description":"The health endpoint is used to determine the current version of the RapidLEI API service e.g.
\n{\n\"version\": \"3.7.12\"\n}\n\nThe Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. The OAuth2 specification (RFC 6749) requires this content type for token requests. Any other content-type will break OAuth2 compliant clients compatibility.
\n","key":"Content-Type","name":"Content-Type","type":"text","value":"application/x-www-form-urlencoded"},{"description":"The Accept request-header field can be used to specify certain media types which are acceptable for the response. The Accept request HTTP header advertises which content types, expressed as MIME types, the client is able to understand.
\n","key":"Accept","type":"text","value":"application/json"}],"body":{"mode":"urlencoded","urlencoded":[{"key":"grant_type","value":"client_credentials","description":"The grant_type parameter must be set to client_credentials
\n","type":"text"},{"key":"client_id","value":"reseller.email@test.com","description":"The client_id parameter must be set to reseller email address
\n","type":"text"},{"key":"client_secret","value":"xxxxxxAPI_key_from_My_Settingsxxxxxx","description":"The client_secret parameter must be set to API key
\n","type":"text"}]},"url":"https://api.rapidlei.com/v1/auth/token","description":"This call requires an API Key from the 'My Settings' section of your account and the email address of the account. It delivers a Bearer Access Token to authenticate subsequent requests and a time to expiry in seconds. Within the Staging Environment the bearer token lasts for 3000 seconds (Allowing for manual use within a Postman collection), but within production this is limited to 900 seconds.
\n","urlObject":{"protocol":"https","path":["v1","auth","token"],"host":["api","rapidlei","com"],"query":[],"variable":[]}},"response":[{"id":"fc2b33ef-146a-4be7-879c-646205990076","name":"Successful Response – access_token, token_type, expires_in parameters returned","originalRequest":{"method":"POST","header":[{"key":"Content-Type","name":"Content-Type","value":"application/x-www-form-urlencoded","type":"text"},{"key":"Accept","value":"application/json","type":"text"}],"body":{"mode":"urlencoded","urlencoded":[{"key":"grant_type","value":"client_credentials","description":"The grant_type parameter must be set to client_credentials","type":"text"},{"key":"client_id","value":"reseller.email@test.com","description":"The client_id parameter must be set to reseller email address","type":"text"},{"key":"client_secret","value":"123456789ABCDEF","description":"The client_secret parameter must be set to API key","type":"text"}]},"url":"https://api.rapidlei.com/v1/auth/token"},"status":"OK","code":200,"_postman_previewlanguage":"json","header":[{"key":"Content-Type","value":"application/json","description":"","type":"text"},{"key":"Cache-Control","value":"no-store","description":"","type":"text"},{"key":"Pragma","value":"no-cache","description":"","type":"text"}],"cookie":[],"responseTime":null,"body":"{\n \"access_token\": \"MTQ0NjJkZmQ5OTM2NDE1ZTZjNGZmZjI3\",\n \"token_type\": \"bearer\",\n \"expires_in\": 30000\n}"},{"id":"93356cf9-46a7-42ca-8f77-cd9c018540d3","name":"Unsuccessful Request – Client Authentication Failed","originalRequest":{"method":"POST","header":[{"key":"Content-Type","name":"Content-Type","value":"application/x-www-form-urlencoded","type":"text"},{"key":"Accept","value":"application/json","type":"text"}],"url":"https://api.rapidlei.com/v1/auth/token"},"status":"Unauthorized","code":401,"_postman_previewlanguage":"json","header":[{"key":"Content-Type","value":"application/json","description":"","type":"text"},{"key":"Cache-Control","value":"no-store","description":"","type":"text"},{"key":"Pragma","value":"no-cache","description":"","type":"text"}],"cookie":[],"responseTime":null,"body":"{\r\n \"orderStatus\": \"authorization_error\",\r\n \"message\": \" Client Authentication failed due to either an invalid client_id (email address) or client_secret (API key from My Settings)\",\r\n \"errorUri\": \"https://rapidlei.com/api\"\r\n}"},{"id":"355a9fcf-50f7-44b0-8e23-0338852ed475","name":"Unsuccessful Request – Missing Request Parameter","originalRequest":{"method":"POST","header":[{"key":"Content-Type","name":"Content-Type","value":"application/x-www-form-urlencoded","type":"text"},{"key":"Accept","value":"application/json","type":"text"}],"body":{"mode":"urlencoded","urlencoded":[{"key":"grant_type","value":"client_credentials","description":"The grant_type parameter must be set to client_credentials","type":"text"},{"key":"client_id","value":"reseller.email@test.com","description":"The client_id parameter must be set to reseller email address","type":"text"}]},"url":"https://api.rapidlei.com/v1/auth/token"},"status":"Bad Request","code":400,"_postman_previewlanguage":"json","header":[{"key":"Content-Type","value":"application/json","description":"","type":"text"},{"key":"Cache-Control","value":"no-store","description":"","type":"text"},{"key":"Pragma","value":"no-cache","description":"","type":"text"}],"cookie":[],"responseTime":null,"body":"{\r\n \"orderStatus\": \"invalid_request\",\r\n \"message\": \"Request is missing the 'client_secret' parameter\",\r\n\t\"errorUri\": \"https://rapidlei.com/api\"\r\n}"},{"id":"ea39ea3c-9588-4b11-aacf-c71eb685776d","name":"Unsuccessful Request – Internal Server Error or Exception","originalRequest":{"method":"POST","header":[{"key":"Content-Type","name":"Content-Type","value":"application/x-www-form-urlencoded","type":"text"},{"key":"Accept","value":"application/json","type":"text"}],"body":{"mode":"urlencoded","urlencoded":[{"key":"grant_type","value":"client_credentials","description":"The grant_type parameter must be set to client_credentials","type":"text"},{"key":"client_id","value":"reseller.email@test.com","description":"The client_id parameter must be set to reseller email address","type":"text"},{"key":"client_secret","value":"123456789ABCDEF","description":"The client_secret parameter must be set to API key","type":"text"}]},"url":"https://api.rapidlei.com/v1/auth/token"},"status":"Internal Server Error","code":500,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\r\n \"orderStatus\": \"server_error\",\r\n \"message\": \"Internal server error - If this problem persists, please contact the support team\",\r\n \"errorUri\": \"https://rapidlei.com/api\"\r\n}"},{"id":"3591146b-02a9-45ee-b0ce-b7a0e437affe","name":"Unsuccessful Request – Unsupported or Missing Grant Type","originalRequest":{"method":"POST","header":[{"key":"Content-Type","name":"Content-Type","value":"application/x-www-form-urlencoded","type":"text"},{"key":"Accept","value":"application/json","type":"text"}],"body":{"mode":"urlencoded","urlencoded":[{"key":"grant_type","value":"password","description":"The grant_type parameter must be set to client_credentials","type":"text"},{"key":"client_id","value":"reseller.email@test.com","description":"The client_id parameter must be set to reseller email address","type":"text"},{"key":"client_secret","value":"123456789ABCDEF","description":"The client_secret parameter must be set to API key","type":"text"}]},"url":"https://api.rapidlei.com/v1/auth/token"},"status":"Bad Request","code":400,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\r\n \"orderStatus\": \"unsupported_grant_type\"\r\n}"}],"_postman_id":"119acd6d-3486-46f0-b70b-f3a139dc79a0"},{"name":"Accounts - User Information","id":"2edadf1b-8f2d-496b-9ad6-c66a86e7c151","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"GET","header":[{"key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"key":"Content-Type","type":"text","value":"application/json"}],"url":"https://api.rapidlei.com/v1/accounts/userinfo","description":"The userinfo endpoint is a secured API that returns basic information about the authenticated user.
\n","urlObject":{"protocol":"https","path":["v1","accounts","userinfo"],"host":["api","rapidlei","com"],"query":[],"variable":[]}},"response":[],"_postman_id":"2edadf1b-8f2d-496b-9ad6-c66a86e7c151"},{"name":"Accounts - Create User","id":"d2648067-1754-458c-9aaf-e793b0307224","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.
\n","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity.
\n","key":"Content-Type","type":"text","value":"application/json"}],"body":{"mode":"raw","raw":"{\r\n \"firstName\": \"Peter\",\r\n \"lastName\": \"Anderson\",\r\n \"email\": \"useremail@server.com\",\r\n \"leiNumber\": \"984500B12AE2CF0PF040\"\r\n}"},"url":"https://api.rapidlei.com/v1/accounts/users","description":"This endpoint adds a new user to the RapidLEI platform. A bearer access token from 'Authentication - Request Access Token' is required to submit the request. The new user's account will be linked to the Partners' LEI provided in the call. All users added to the platform will need to complete the registration process and agree to terms before being added. An email based challenge/response to the email address provided in the call verifies permission and email accuracy. If the challenge is not completed within 6 days, the entry will be deleted from the system (GDPR Privacy by Design). A web based system is available too. See 'Referral Link' details on https://rapidlei.com/partners/partner-resources/
\nPlease note that the Staging System does not have any ability to send emails other than to a default catchall of testing(a)rapidlei.com, so please discuss with the support team support(a)rapidlei.com to be able to test this function.
\nFinally, please note that you may be enabled to use this API call, but not the 'Full' LEI API. Please discuss with the support team support(a)rapidlei.com
\n","urlObject":{"protocol":"https","path":["v1","accounts","users"],"host":["api","rapidlei","com"],"query":[],"variable":[]}},"response":[{"id":"bb0c85f9-5546-4f1e-880b-468eef86d660","name":"Successful Response – User Created","originalRequest":{"method":"POST","header":[{"key":"Authorization","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx","description":"he Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","type":"text"},{"key":"Content-Type","value":"application/json","description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","type":"text"}],"body":{"mode":"raw","raw":"{\r\n \"firstName\": \"Peter\",\r\n \"lastName\": \"Anderson\",\r\n \"email\": \"useremail@server.com\",\r\n \"leiNumber\": \"984500B12AE2CF0PF040\",\r\n \"organizationName\": \"Legal Entity Name Limited\"\r\n}","options":{"raw":{"language":"json"}}},"url":"https://api.rapidlei.com/v1/accounts/users"},"status":"OK","code":200,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"message\": \"User created successfully.\"\n}"},{"id":"da429a91-33c9-4454-b2fd-296da441eb29","name":"Unsuccessful Response – Referrer LEI is not found or not managed by RapidLEI","originalRequest":{"method":"POST","header":[{"key":"Authorization","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx","description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","type":"text"},{"key":"Content-Type","value":"application/json","description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","type":"text"}],"body":{"mode":"raw","raw":"{\r\n \"firstName\": \"Peter\",\r\n \"lastName\": \"Anderson\",\r\n \"email\": \"useremail@server.com\",\r\n \"leiNumber\": \"123400B12AE2CF0PF040\",\r\n \"organizationName\": \"Legal Entity Name Limited\"\r\n}","options":{"raw":{"language":"json"}}},"url":"https://api.rapidlei.com/v1/accounts/users"},"status":"Internal Server Error","code":500,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderStatus\": \"server_error\",\n \"message\": \"The 'leiNumber' parameter needs to be an LEI managed by RapidLEI and linked with your account. Please contact our support team to discuss options.\",\n \"errorUri\": \"https://rapidlei.com/api\"\n}"},{"id":"a4021b75-7f3a-48f3-95eb-cab6c53b2818","name":"Unsuccessful Response – Parameter Missing","originalRequest":{"method":"POST","header":[{"key":"Authorization","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx","description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","type":"text"},{"key":"Content-Type","value":"application/json","description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","type":"text"}],"body":{"mode":"raw","raw":"{\r\n \"lastName\": \"Anderson\",\r\n \"email\": \"useremail@server.com\",\r\n \"leiNumber\": \"984500B12AE2CF0PF040\",\r\n \"organizationName\": \"Legal Entity Name Limited\"\r\n}"},"url":"https://api.rapidlei.com/v1/accounts/users"},"status":"Bad Request","code":400,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderStatus\": \"invalid_request\",\n \"message\": \"Request is missing the 'firstName' parameter\",\n \"errorUri\": \"https://rapidlei.com/api\"\n}"},{"id":"53fceb45-f783-4156-ac12-0109e00ab47e","name":"Unsuccessful Response – Invalid Email Address","originalRequest":{"method":"POST","header":[{"key":"Authorization","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx","description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","type":"text"},{"key":"Content-Type","value":"application/json","description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","type":"text"}],"body":{"mode":"raw","raw":"{\r\n \"firstName\": \"Peter\",\r\n \"lastName\": \"Anderson\",\r\n \"email\": \"useremailserver.com\",\r\n \"leiNumber\": \"984500B12AE2CF0PF040\",\r\n \"organizationName\": \"Legal Entity Name Limited\"\r\n}","options":{"raw":{"language":"json"}}},"url":"https://api.rapidlei.com/v1/accounts/users"},"status":"Bad Request","code":400,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{ \r\n \"orderStatus\": \"invalid_request\", \r\n \"message\": \"Please provide a valid email address format user@domain.com or first.last@domain.co.uk etc\", \r\n \"errorUri\": \"https://rapidlei.com/api\" \r\n}"},{"id":"b9d94cb6-95ce-44f3-9a95-1b3b8aefe0f9","name":"Unsuccessful Response – Invalid LEI Format","originalRequest":{"method":"POST","header":[{"key":"Authorization","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx","description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","type":"text"},{"key":"Content-Type","value":"application/json","description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","type":"text"}],"body":{"mode":"raw","raw":"{\r\n \"firstName\": \"Peter\",\r\n \"lastName\": \"Anderson\",\r\n \"email\": \"useremail@server.com\",\r\n \"leiNumber\": \"984500B12AE2CF0PF0\",\r\n \"organizationName\": \"Legal Entity Name Limited\"\r\n}","options":{"raw":{"language":"json"}}},"url":"https://api.rapidlei.com/v1/accounts/users"},"status":"Bad Request","code":400,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderStatus\": \"invalid_request\",\n \"message\": \"Please ensure the 'leiNumber' is a valid ISO 17442 format LEI (20 characters).\",\n \"errorUri\": \"https://rapidlei.com/api\"\n}"},{"id":"e15b220b-5f60-4e96-b806-2f6ef1332ce1","name":"Unsuccessful Response – Request to add user failed as the user already exists","originalRequest":{"method":"POST","header":[{"key":"Authorization","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx","description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","type":"text"},{"key":"Content-Type","value":"application/json","description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","type":"text"}],"body":{"mode":"raw","raw":"{\r\n \"firstName\": \"Peter\",\r\n \"lastName\": \"Anderson\",\r\n \"email\": \"useremail@server.com\",\r\n \"lei\": \"984500B12AE2CF0PF040\",\r\n \"organizationName\": \"Legal Entity Name Limited\"\r\n}","options":{"raw":{"language":"json"}}},"url":"https://api.rapidlei.com/v1/accounts/users"},"status":"Internal Server Error","code":500,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderStatus\": \"server_error\",\n \"message\": \"We already have a user account with the email address supplied. If in doubt please contact our support team.\",\n \"errorUri\": \"https://rapidlei.com/api\"\n}"},{"id":"31789aa3-07f2-4b00-b6f7-136324dde759","name":"Unsuccessful Response – Referrer feature is not enabled","originalRequest":{"method":"POST","header":[{"key":"Authorization","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx","description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","type":"text"},{"key":"Content-Type","value":"application/json","description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","type":"text"}],"body":{"mode":"raw","raw":"{\r\n \"firstName\": \"Peter\",\r\n \"lastName\": \"Anderson\",\r\n \"email\": \"useremail@server.com\",\r\n \"leiNumber\": \"984500B12AE2CF0PF040\",\r\n \"organizationName\": \"Legal Entity Name Limited\"\r\n}","options":{"raw":{"language":"json"}}},"url":"https://api.rapidlei.com/v1/accounts/users"},"status":"Internal Server Error","code":500,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderStatus\": \"server_error\",\n \"message\": \"Sorry, you are unable to add users. The Referrer feature has not been enabled for your account. If in doubt, please talk to our support team.\",\n \"errorUri\": \"https://rapidlei.com/api\"\n}"},{"id":"8edbdaf2-28e2-4854-9679-406464fb672b","name":"Unsuccessful Response – Parameter Length Error","originalRequest":{"method":"POST","header":[{"key":"Authorization","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx","description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","type":"text"},{"key":"Content-Type","value":"application/json","description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","type":"text"}],"body":{"mode":"raw","raw":"{\r\n \"firstName\": \"Peter middle name example is much bigger than we allow\",\r\n \"lastName\": \"Anderson\",\r\n \"email\": \"useremail@server.com\",\r\n \"leiNumber\": \"984500B12AE2CF0PF040\",\r\n \"organizationName\": \"Legal Entity Name Limited\"\r\n}","options":{"raw":{"language":"json"}}},"url":"https://api.rapidlei.com/v1/accounts/users"},"status":"Bad Request","code":400,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderStatus\": \"invalid_request\",\n \"message\": \"Parameter 'firstName' should not be greater than 50 characters\",\n \"errorUri\": \"https://rapidlei.com/api\"\n}"},{"id":"26787d39-2a17-4d8f-873f-2aa9f9ab8168","name":"Unsuccessful Response – Missing organizaionName","originalRequest":{"method":"POST","header":[{"key":"Authorization","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx","description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","type":"text"},{"key":"Content-Type","value":"application/json","description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","type":"text"}],"body":{"mode":"raw","raw":"{\r\n \"firstName\": \"Peter\",\r\n \"lastName\": \"Anderson\",\r\n \"email\": \"useremail@server.com\",\r\n \"leiNumber\": \"984500B12AE2CF0PF040\"\r\n}","options":{"raw":{"language":"json"}}},"url":"https://api.rapidlei.com/v1/accounts/users"},"status":"Bad Request","code":400,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderStatus\": \"invalid_request\",\n \"message\": \"Request is missing the 'organizaionName' parameter\",\n \"errorUri\": \"https://rapidlei.com/api\"\n}"}],"_postman_id":"d2648067-1754-458c-9aaf-e793b0307224"},{"name":"LEI – Query Supported Jurisdictions","id":"e3d104ac-f6c2-4fdf-9765-5260e887ece3","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"GET","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.
\n","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity.
\n","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://api.rapidlei.com/v1/jurisdictions","description":"This API call is used to query supported jurisdictions and confidence levels. Confidence level 10 is fully automated including Authorised Representative verification resulting in rapid, efficient LEI issuance. Confidence level 0 is a manually processed jurisdiction requiring manual verification of data on the business registry. Confidence levels 1-9 indicate the expected confidence level in gathering data from the registry. 9 indicates all LE-RD Level 1 data is usually available. 8 indicates most LE-RD Level 1 data is usually available. For additional details on how best to use this function please contact the RapidLEI support team.
\n","urlObject":{"protocol":"https","path":["v1","jurisdictions"],"host":["api","rapidlei","com"],"query":[],"variable":[]}},"response":[{"id":"34afa8b8-8305-410b-9bb1-48e5a2e685d8","name":"Successful Response – List of Jurisdictions returned","originalRequest":{"method":"GET","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://api.rapidlei.com/v1/jurisdictions"},"status":"OK","code":200,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"countries\": [\n {\n \"jurisdiction\": \"DK\",\n \"confidenceLevel\": \"10\"\n },\n {\n \"jurisdiction\": \"HK\",\n \"confidenceLevel\": \"0\"\n },\n {\n \"jurisdiction\": \"NL\",\n \"confidenceLevel\": \"7\"\n }\n ],\n \"states\": [\n\t {\n\t \"jurisdiction\": \"US-KS\",\n\t \"confidenceLevel\": \"10\"\n\t },\n\t {\n\t \"jurisdiction\": \"US-NJ\",\n\t \"confidenceLevel\": \"6\"\n\t },\n\t {\n\t \"jurisdiction\": \"US-DC\",\n\t \"confidenceLevel\": \"0\"\n\t }\n ]\n}"},{"id":"20de2b52-b983-41fe-87f8-e57ba1a178bb","name":"Unsuccessful Response - User not allowed to use the Full API, only the ‘Create User’ endpoint","originalRequest":{"method":"GET","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://api.rapidlei.com/v1/jurisdictions"},"status":"Unauthorized","code":401,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderStatus\": \"authorization_error\",\n \"message\": \"You do not have the ability to use the Full RapidLEI API from this account – you are configured only to use the ‘Create User’ endpoint, please contact our support team on support@rapidlei.com\",\n \"errorUri\": \"https://rapidlei.com/api\"\n}"},{"id":"5a55d04c-a024-4d6a-9a0e-fb8eaa7d863f","name":"Unsuccessful Response - Unknown Error or Exception during processing request","originalRequest":{"method":"GET","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://api.rapidlei.com/v1/jurisdictions"},"status":"Internal Server Error","code":500,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderStatus\": \"server_error\",\n \"message\": \"We've been unable to process your request - please contact our support team.\",\n \"errorUri\": \"https://rapidlei.com/api\"\n}"}],"_postman_id":"e3d104ac-f6c2-4fdf-9765-5260e887ece3"},{"name":"LEI – Pre-Submission Entity Search","id":"3180743c-e8c2-48e2-8d7f-f7909b398334","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.
\n","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity.
\n","key":"Content-Type","name":"Content-Type","type":"text","value":"application/json"}],"body":{"mode":"raw","raw":"{\r\n \"keyword\": \"Ubisecure Holdings\",\r\n \"legalJurisdiction\": \"GB\",\r\n \"entityType\": \"GENERAL\"\r\n}","options":{"raw":{"language":"json"}}},"url":"https://api.rapidlei.com/v1/leis/searchByKeyword","description":"The Pre-Submission Entity Search ensures data accuracy for New LEI or Import LEI requests by performing an initial search of the jurisdiction. Legal Name spelling, form and capitalization as well as Registration Authority Entity ID (Business Registry Number) accuracy are improved using this API endpoint. The API Endpoint returns one or more potential legal entities along with a 'searchId' and 'companyId' - Please see LEI – Create New LEI and LEI – Import Existing LEI for details.
\nIt is highly recommended to search by the Business Registry Number first as this is the most accurate method. The name of the Legal Entity may be too generic and may return too many results to display all, resulting in the entity not being found.
\nThe keyword helps identify the Legal Entity. It can be either:
\nName of the Legal Entity e.g. ABC Limited
\nCompany Number for the Legal Entity e.g. 68678678
\nThe LEI number to be imported/transferred. e.g. 89450051ZRDOL9KEWH63
\nlegalJurisdiction
\nA supported legal jurisdiction is required. e.g. DK or US-CA for California in the United States
\nPlease note that the following entityType's are NOT supported within the pre-submission search:-
\nThe Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.
\n","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity.
\n","key":"Content-Type","name":"Content-Type","type":"text","value":"application/json"}],"body":{"mode":"raw","raw":"{\n \"companyName\": \"ABC Limited\",\n \"companyNumber\": \"68678678\",\n \"searchId\": \"9cf0521c2dfc4502bfa3f7bb49daca77\",\n \"companyId\": \"8ba68d90a7324ba2bbbbe87bc227c461\",\n \"legalJurisdiction\": \"DK\",\n \"firstName\": \"Peter\",\n \"lastName\": \"Anderson\",\n \"isLevel2DataAvailable\": false,\n \"reportingExceptionReason\": \"NATURAL_PERSONS\",\n \"multiYearSupport\": 3,\n \"entityType\": \"GENERAL\",\n \"userComments\": \"optional comments\",\n \"notificationUrl\": \"https://www.someotherserver.com/notify/me/when/lei/is/ready\",\n \"notificationToken\": \"Sq31YkqGWKXGEpeJGZwM\",\n \"loaFile\": {\n \"fileName\": \"My Letter of Authorization.docx\",\n \"fileUrl\": \"http://www.example.com/LoA.docx?token=GFVHGSahG6HGjsggdgxxSecurity-Token-examplexxGFDsdd\"\n },\n \"corroboratingFiles\": [\n {\n \"fileName\": \"Corroborating Data 1.docx\",\n \"fileUrl\": \"http://www.example.com/file.docx\"\n },\n {\n \"fileName\": \" Corroborating Data 2.docx\",\n \"fileData\": \"data:application/octet–stream;base64, ldfhaklsjdfhkasjfjsdfgakjsfgakjsdagsdf...\"\n }\n ]\n}"},"url":"https://api.rapidlei.com/v1/leis/orders/create","description":"This API endpoint initiates the workflow process to request a new LEI (i.e. An LEI will be created, so the call assumes that the Legal Entity does not already have an LEI, but it also tests that assumption and will provide an error if one is found - see the examples for more information). The bearer access Token from 'Authentication - Request Access Token' is required to submit the request along with the following mandatory / optional parameters.
\nPlease note GDPR (General Data Protection Regulations) when transferring personal data. Ensure permission of the Legal Entity.
\ncompanyName
Name of the Legal Entity noting that accuracy here helps the overall process flow and accuracy of any potential duplicate test. e.g. ABC Limited
companyNumber
Company Number, (Registration Authority Entity ID) for the Legal Entity noting that accuracy here helps the overall process flow and accuracy of any potential duplicate test. e.g. 068678678 - Tip - don't forget to ensure any leading '0's are maintained - this is common for UK based numbers. For Funds which sometimes do not have a Registration Authority Entity ID, you may leave this field empty ensuring entityType is set to FUND. There may be a legitimate edge case such as a Legal Entity in Germany, or South Carolina which does not have any number. In these rare cases please use entityType OTHER
legalJurisdiction
A supported legal jurisdiction is required. e.g. DK or US-CA for California in the United States
firstName
The First Name(s) of the Authorised Representative with the responsibility/authority to request and approve the creation of an LEI e.g. Peter
lastName
The Last Name of the Authorised Representative e.g. Anderson
isLevel2DataAvailable
A Boolean value - If the Legal Entity consolidates accounts with parental entities, then Level 2 data will be required. This data is not to be provided by API calls. Due to the complex nature of the data possibilities, the GUI interface of the RapidLEI Identity Platform must be used i.e. true if level 2 data is available and false if reporting exceptions are to be used.
multiYearSupport
An integer from 1 to 5. Please see https://rapidlei.com/lei-pricing/ for details. Please default to 1 as the standard option.
reportingExceptionReason
If isLevel2DataAvailable is set to false, then it indicates there is no level 2 information, so please highlight the appropriate reporting exception reason which will be used for BOTH Direct and Ultimate Parent reporting. If any other combination of reporting exceptions is required, please set isLevel2DataAvailable to true and use the GUI
NATURAL_PERSONS
\nNON_CONSOLIDATING
\nNO_KNOWN_PERSON
\nPrior to the release of LE-RR Version 2.1, the following reasons were specifically used for Level 2 scenarios where parental accounting was present, but LEI details were absent. The removal of PNI data by the ROC (Regulatory Oversight Committee) has deprecated these exception reasons. Please see this announcement for details (https://www.leiroc.org/publications/gls/roc_20220107.pdf)
\nDeprecated exception reasons:-
\nCONSENT_NOT_OBTAINED
\nLEGAL_OBSTACLES
\nBINDING_LEGAL_COMMITMENTS
\nDETRIMENT_NOT_EXCLUDED
\nDISCLOSURE_DETRIMENTAL
\nHave been replaced by a single reporting exception configured within the GUI along with other level 2 parental reporting and Fund reporting options:-
\nsearchId & companyId
When the LEI – Pre-Submission Entity Search function is used prior to a New LEI being created, submission of the 'searchId' and 'companyId' together with the EXACT Name of the companyName, legalJurisdiction and companyNumber will accelerate the speed at which the LEI is issued.
entityType
If entityType is not included, we'll assume the request is for a legal entity. A positive indication of the entityType will increase the efficiency of the RapidLEI vetting team and any associated workflows.
GENERAL
\nSOLE_PROPRIETOR
\nFUND
\nWILL_PENSION
\nTRUST
\nOTHER
\nNotes:- If Submitting a FUND it is advisable to include the fund deed as 'Evidence of Authority' in the corroboratingFiles as this will avoid the need to ask for this document.
\nnotificationUrl
To avoid unnecessary polling, webhooks can be used to pass orderStatus information in real time. A webhook is a user-defined HTTP (ideally HTTPS) endpoints which can accept POST requests for real time synchronous LEI processing. An optional security token may be used to avoid replay attacks, however the notificationUrl may also contain additional URL parameters. Webhook ApS in Denmark, ran by Simon Fredsted, offers a very simple listening service for testing webhooks. Please see https://webhook.site/ for details and usage guidelines. The two parameters returned in the RequestBody are - orderTrackingCode and orderStatus, with the optional security token being returned as notificationTokene.g. https://www.someotherserver.com/notify/me/when/lei/is/ready
or https://www.someotherserver.com/notify/me/when/lei/is/ready?type=exampletype&token=URL_based_token_examplePLEASE NOTE - Redirects are not guaranteed to be supported in all cases therefore please ensure the correct URL and any final / characters in the URL are sent.
notificationToken
An optional unique token to avoid the possibility of a third party accidentally making a call to a static notification URL and therefore maliciously affecting the workflow.
e.g. Sq31YkqGWKXGEpeJGZwM\"
userComments
An optional comment or instruction to aid efficient processing of the LEI by the RapidLEI vetting team – to be used primarily for simple comments < 1000 characters to avoid the need to send additional corroborating documents.
corroboratingFiles Up to 5 additional files which may aid vetting or validation of the Application. Please note the upload limit of 20MB each.
\nnextRenewalDate
nextRenewalDate is an advanced customization option which requires multi-year support and is applicable to enterprises who require alignment of LEI issuance/renewal around specific dates. Please discuss in detail before implementing this function. nextRenewalDate is a date in the future which indicates the 'nextRenewalDate' of the LEI. If omitted, the date will be set to one calendar year from initial issuance of the LEI.
is3rdPartyRequest
If is3rdPartyRequest is set to true an LoA MUST be uploaded which highlights the agreement between the 3rd Party and the Legal Entity. For more details please discuss with our legal team legal(a)rapidlei.com. Please discuss in detail before implementing this function
The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.
\n","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity.
\n","key":"Content-Type","type":"text","value":"application/json"}],"body":{"mode":"raw","raw":"{\n \"companyName\": \"ABC Limited\",\n \"companyNumber\": \"68678678\",\n \"leiNumber\": \"213800855GFRCT277149\",\n \"legalJurisdiction\": \"DK\",\n \"firstName\": \"Peter\",\n \"lastName\": \"Anderson\",\n \"email\": \"peter.anderson@testmail.com\",\n \"phone\": \"003489348573945\",\n \"isLevel2DataAvailable\": false,\n \"reportingExceptionReason\": \"NATURAL_PERSONS\",\n \"multiYearSupport\": 3,\n \"userComments\": \"optional comments\",\n \"notificationUrl\": \"https://www.someotherserver.com/notify/me/when/lei/is/ready\",\n \"notificationToken\": \"Sq31YkqGWKXGEpeJGZwM\",\n \"mergedOrRetiredLeiComments\": \"Optional comments to mention the reasons to import MERGED or RETIRED LEI\",\n \"loaFile\": {\n \"fileName\": \"My Letter of Authorization.docx\",\n \"fileUrl\": \"http://www.example.com/LoA.docx?token=GFVHGSahG6HGjsggdgxxSecurity-Token-examplexxGFDsdd\"\n },\n \"corroboratingFiles\": [\n {\n \"fileName\": \"Corroborating Data 1.docx\",\n \"fileUrl\": \"http://www.example.com/file.docx\"\n },\n {\n \"fileName\": \" Corroborating Data 2.docx\",\n \"fileData\": \"data:application/octet–stream;base64, ldfhaklsjdfhkasjfjsdfgakjsfgakjsdagsdf...\"\n }\n ]\n}"},"url":"https://api.rapidlei.com/v1/leis/orders/import","description":"This API endpoint initiates the workflow process to transfer an existing LEI (i.e. An LEI must already exist and have a GLEIF Status of ISSUED, LAPSED or rarely RETIRED). The bearer access Token from 'Authentication - Request Access Token' is required to submit the request along with the following mandatory / optional parameters.
\nPlease note GDPR (General Data Protection Regulations) when transferring personal data. Ensure permission of the Legal Entity.
\ncompanyName
Name of the Legal Entity noting that accuracy here helps the overall process flow and accuracy of any potential duplicate test. e.g. ABC Limited
companyNumber
Company Number, (Registration Authority Entity ID) for the Legal Entity noting that accuracy here helps the overall process flow and accuracy of any potential duplicate test. e.g. 068678678 - Tip - don't forget to ensure any leading '0's are maintained - this is common for UK based numbers. For Funds which sometimes do not have a Registration Authority Entity ID, you may leave this field empty ensuring entityType is set to FUND. There may be a legitimate edge case such as a Legal Entity in Germany, or South Carolina which does not have any number. In these rare cases please use entityType OTHER
legalJurisdiction
A supported legal jurisdiction is required. e.g. DK or US-CA for California in the United States
leiNumber
The LEI number to be imported/transferred.
e.g. 89450051ZRDOL9KEWH63
firstName
The First Name(s) of the Authorised Representative with the responsibility/authority to request and approve the creation of an LEI e.g. Peter
lastName
The Last Name of the Authorised Representative e.g. Anderson
email
The email of the contact person who is authorized to request the transfer of the LEI e.g. peter.anderson@testmail.com (Please note that this is a requirement of the GLEIF LEI Transfer Protocol and must be transferred as part of the initial call. This differs from the creation of an LEI where this information is not usually taken – please ensure permission of the Legal Entity to allow the transfer of this personal data)
phone
The phone number of the contact person who is authorized to request the transfer of the LEI e.g. 003489348573945 (Please note that this is a requirement of the GLEIF LEI Transfer Protocol and must be transferred as part of the initial call. This differs from the creation of an LEI where this information is not usually taken – please ensure permission of the Legal Entity to allow the transfer of this personal data)
isLevel2DataAvailable
A Boolean value - If the Legal Entity consolidates accounts with parental entities, then Level 2 data will be required. This data is not to be provided by API calls. Due to the complex nature of the data possibilities, the GUI interface of the RapidLEI Identity Platform must be used i.e. true if level 2 data is available and false if reporting exceptions are to be used.
multiYearSupport
An integer from 1 to 5. Please see https://rapidlei.com/lei-pricing/ for details. Please default to 1 as the standard option.
reportingExceptionReason
If isLevel2DataAvailable is set to false, then it indicates there is no level 2 information, so please highlight the appropriate reporting exception reason which will be used for BOTH Direct and Ultimate Parent reporting. If any other combination of reporting exceptions is required, please set isLevel2DataAvailable to true and use the GUI
NATURAL_PERSONS
\nNON_CONSOLIDATING
\nNO_KNOWN_PERSON
\nPrior to the release of LE-RR Version 2.1, the following reasons were specifically used for Level 2 scenarios where parental accounting was present, but LEI details were absent. The removal of PNI data by the ROC (Regulatory Oversight Committee) has deprecated these exception reasons. Please see this announcement for details (https://www.leiroc.org/publications/gls/roc_20220107.pdf)
\nDeprecated exception reasons:-
\nCONSENT_NOT_OBTAINED
\nLEGAL_OBSTACLES
\nBINDING_LEGAL_COMMITMENTS
\nDETRIMENT_NOT_EXCLUDED
\nDISCLOSURE_DETRIMENTAL
\nHave been replaced by a single reporting exception configured within the GUI along with other level 2 parental reporting and Fund reporting options:-
\nentityType
If entityType is not included, we'll assume the request is for a legal entity. A positive indication of the entityType will increase the efficiency of the RapidLEI vetting team and any associated workflows.
GENERAL
\nSOLE_PROPRIETOR
\nFUND
\nWILL_PENSION
\nTRUST
\nOTHER
\nNotes:- If Submitting a FUND it is advisable to include the fund deed as 'Evidence of Authority' in the corroboratingFiles as this will avoid the need to ask for this document.
\nnotificationUrl
To avoid unnecessary polling, webhooks can be used to pass orderStatus information in real time. A webhook is a user-defined HTTP (ideally HTTPS) endpoints which can accept POST requests for real time synchronous LEI processing. An optional security token may be used to avoid replay attacks, however the notificationUrl may also contain additional URL parameters. Webhook ApS in Denmark, ran by Simon Fredsted, offers a very simple listening service for testing webhooks. Please see https://webhook.site/ for details and usage guidelines. The two parameters returned in the RequestBody are - orderTrackingCode and orderStatus, with the optional security token being returned as notificationTokene.g. https://www.someotherserver.com/notify/me/when/lei/is/ready
or https://www.someotherserver.com/notify/me/when/lei/is/ready?type=exampletype&token=URL_based_token_examplePLEASE NOTE - Redirects are not guaranteed to be supported in all cases therefore please ensure the correct URL and any final / characters in the URL are sent.
notificationToken
An optional unique token to avoid the possibility of a third party accidentally making a call to a static notification URL and therefore maliciously affecting the workflow.
e.g. Sq31YkqGWKXGEpeJGZwM\"
userComments
An optional comment or instruction to aid efficient processing of the LEI by the RapidLEI vetting team – to be used primarily for simple comments < 1000 characters to avoid the need to send additional corroborating documents.
corroboratingFiles Up to 5 additional files which may aid vetting or validation of the Application. Please note the upload limit of 20MB each.
\nnextRenewalDate
nextRenewalDate is an advanced customization option which requires multi-year support and is applicable to enterprises who require alignment of LEI issuance/renewal around specific dates. Please discuss in detail before implementing this function. nextRenewalDate is a date in the future which indicates the 'nextRenewalDate' of the LEI. If omitted, the date will be set to one calendar year from initial issuance of the LEI.
is3rdPartyRequest
If is3rdPartyRequest is set to true an LoA MUST be uploaded which highlights the agreement between the 3rd Party and the Legal Entity. For more details please discuss with our legal team legal(a)rapidlei.com. Please discuss in detail before implementing this function
The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.
\n","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity.
\n","key":"Content-Type","name":"Content-Type","type":"text","value":"application/json"}],"body":{"mode":"raw","raw":"{\n \"orderTrackingCode\": \"YEaadmjQbt00uY0mepcg\",\n \"loaFiles\": [\n {\n \"fileName\": \"LoA1. pdf\",\n \"fileData\": \"data:text/plain;base64,dGVzdA==\"\n },\n {\n \"fileName\": \"LoA2.pdf\",\n \"fileUrl\": \"https://www.lean.org/downloads/sampleboardreport.pdf\"\n }\n ], \n \"eoaFiles\": [\n {\n \"fileName\": \"EoaFile1.docx\",\n \"fileData\": \"data:text/plain;base64,dGVzdA==\"\n },\n {\n \"fileName\": \"EoaFile2.pdf\",\n \"fileUrl\": \"https://www.lean.org/downloads/sampleboardreport.pdf\"\n }\n ],\n \"corroboratingFiles\": [\n {\n \"fileName\": \"CorroboratingFile1.docx\",\n \"fileData\": \"data:text/plain;base64,dGVzdA==\"\n },\n {\n \"fileName\": \"CorroboratingFile2.pdf\",\n \"fileUrl\": \"https://www.lean.org/downloads/sampleboardreport.pdf\"\n }\n ]\n}"},"url":"https://api.rapidlei.com/v1/leis/uploadFiles","description":"This API endpoint mimics the GUI facility to upload files at any time, for any LEI order with an associated ‘orderTrackingCode’. Files can be of type LoA (Letter of Authorization), EoA (Evidence of Authority) or other Corroborating Data. Orders submitted via GUI (Graphical User Interface) or via Bulk XLS methods, do not have unique API ‘orderTrackingCode’ and therefore files must be associated with these orders using the GUI interface only. The bearer access Token from 'Authentication - Request Access Token' is required to submit the request along with the following mandatory / optional parameters.
\n– orderTrackingCode
\nA unique token returned when any New, Import or Renew order is created. e.g. 987a9sd8f7a9sd8f7
\nloaFiles
A Letter of Authorization (LoA) is used to provide linkage between the Applicant applying for the LEI & a Valid Authorised Representative found on a Registry for the Legal Entity. The Applicant applying for the LEI will be the Signing Authority name submitted as firstName lastName parameters. The Letter of Authorization (LoA) will be a document from one of the Valid Authorised Representatives, this document will state that the valid signer is empowering the Applicant of the LEI (Authorised Representative Name already given) to manage the LEI on their behalf. Please note that if a valid Authorised Signing Authority wishes to manage the LEI themselves directly then the Authorised Representative Name provided in the order creation can be amended in the GUI.
eoaFiles
Evidence of Authority (EoA) is used to provide additional clarification/evidence of the empowered Authorised Representative name submitted as firstName lastName parameters. A typical common example would be Articles of Association for an LLC in Delaware in the United States which does not maintain records of empowered individuals within their registry. For more details, please discuss with our legal team legal(a)rapidlei.com. Multiple EoA's may be submitted using either the fileData method or fileUrl method. Up to 10 additional files may be uploaded.
corroboratingFiles
Up to 10 additional files which may aid vetting or validation of the Application. Please note the upload limit of 20MB each.
The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.
\n","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity.
\n","key":"Content-Type","name":"Content-Type","type":"text","value":"application/json"}],"body":{"mode":"raw","raw":"{\n \"orderTrackingCode\": \"987a9sd8f7a9sd8f7\",\n \"userComments\": \"Page 10 of the annual report details the level 2 parental structure your vetting team needs\"\n}"},"url":"https://api.rapidlei.com/v1/leis/uploadComments","description":"This API endpoint mimics the GUI facility to upload comments at any time, for any LEI order with an associated ‘orderTrackingCode’. Comments help provide our vetting team with essential details to help process LEI applications more efficiently
\n– orderTrackingCode
\nA unique token returned when any New, Import or Renew order is created. e.g. 987a9sd8f7a9sd8f7
\n– userComments
\nA comment or instruction to aid efficient processing of the LEI by the RapidLEI vetting team – to be used primarily for simple comments < 1000 characters to avoid the need to send additional corroborating documents.
\n","urlObject":{"protocol":"https","path":["v1","leis","uploadComments"],"host":["api","rapidlei","com"],"query":[],"variable":[]}},"response":[{"id":"f57c9785-5ab8-4cc2-8e90-694dc3fa3d7c","name":"Successful Response – Comments Submitted Successfully","originalRequest":{"method":"POST","header":[{"key":"Authorization","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx","description":"A Bearer Token must be set to a valid access token in the Authorization header","type":"text"},{"key":"Content-Type","name":"Content-Type","value":"application/json","description":"The Accept header is used by HTTP clients to tell the server what content types they'll accept.","type":"text"}],"body":{"mode":"raw","raw":"{\r\n \"orderTrackingCode\": \"987a9sd8f7a9sd8f7\",\r\n \"userComments\": \"Page 10 of the annual report details the level 2 parental structure your vetting team needs\"\r\n}","options":{"raw":{"language":"json"}}},"url":"https://api.rapidlei.com/v1/leis/uploadComments"},"status":"OK","code":200,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderTrackingCode\": \"987a9sd8f7a9sd8f7\",\n \"message\": \"userComments successfully submitted\"\n}"},{"id":"c5b94998-503d-4878-9eff-1b9175308477","name":"Unsuccessful Response – All Parameters or entire JSON body missing Copy","originalRequest":{"method":"POST","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"key":"Content-Type","name":"Content-Type","value":"application/json","description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","type":"text"}],"body":{"mode":"raw","raw":"{}","options":{"raw":{"language":"json"}}},"url":"https://api.rapidlei.com/v1/leis/uploadComments"},"status":"Bad Request","code":400,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\r\n \"orderStatus\": \"invalid_request\",\r\n \"message\": \"The request is missing mandatory parameters. Please check our API documentation available at https://rapidlei.com/developers\",\r\n \"errorUri\": \"https://rapidlei.com/api\"\r\n}"},{"id":"67f89022-529a-4f47-a445-eaeff673a9c1","name":"Unsuccessful Response – 'orderTrackingCode' Parameter Missing","originalRequest":{"method":"POST","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"key":"Content-Type","name":"Content-Type","value":"application/json","description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","type":"text"}],"body":{"mode":"raw","raw":"{\r\n \"userComments\": \"Page 10 of the annual report details the level 2 parental structure your vetting team needs\"\r\n}","options":{"raw":{"language":"json"}}},"url":"https://api.rapidlei.com/v1/leis/uploadComments"},"status":"Bad Request","code":400,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\r\n \"orderStatus\": \"invalid_request\",\r\n \"message\": \"Request is missing the 'orderTrackingCode' parameter\",\r\n \"errorUri\": \"https://rapidlei.com/api\"\r\n}"},{"id":"530b6ae7-4703-4a7e-bde0-c1970b634c11","name":"Unsuccessful Response – 'userComments' Parameter Missing Copy","originalRequest":{"method":"POST","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"key":"Content-Type","name":"Content-Type","value":"application/json","description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","type":"text"}],"body":{"mode":"raw","raw":"{\r\n \"orderTrackingCode\": \"987a9sd8f7a9sd8f7\"\r\n}","options":{"raw":{"language":"json"}}},"url":"https://api.rapidlei.com/v1/leis/uploadComments"},"status":"Bad Request","code":400,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\r\n \"orderStatus\": \"invalid_request\",\r\n \"message\": \"Request is missing the 'userComments' parameter\",\r\n \"errorUri\": \"https://rapidlei.com/api\"\r\n}"},{"id":"5c5f56a5-d3c5-4c9f-bd0e-9a89588dd404","name":"Unsuccessful Response – Maximum character limit exceeded","originalRequest":{"method":"POST","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"key":"Content-Type","name":"Content-Type","value":"application/json","description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","type":"text"}],"body":{"mode":"raw","raw":"{\r\n \"orderTrackingCode\": \"987a9sd8f7a9sd8f7\",\r\n \"userComments\": \"Well, we seem to have made the comment length too much for the API endpoint to swallow, so we need to reduce this down to less than 2000 characters. Here’s some padding to highlight what 2001 characters looks like 78901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901 makes 2001\"\r\n}","options":{"raw":{"language":"json"}}},"url":"https://api.rapidlei.com/v1/leis/uploadComments"},"status":"Bad Request","code":400,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\r\n \"orderStatus\": \"invalid_request\",\r\n \"message\": \"Parameter 'userComments' should not be greater than 2000 characters.\",\r\n \"errorUri\": \"https://rapidlei.com/api\"}\r\n"},{"id":"ea02a342-f63b-4746-af48-c1044093abad","name":"Unsuccessful Response – invalid 'orderTrackingCode'","originalRequest":{"method":"POST","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"key":"Content-Type","name":"Content-Type","value":"application/json","description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","type":"text"}],"body":{"mode":"raw","raw":"{\r\n \"orderTrackingCode\": \"Mycode\",\r\n \"userComments\": \"Page 10 of the annual report details the level 2 parental structure your vetting team needs\"\r\n}","options":{"raw":{"language":"json"}}},"url":"https://api.rapidlei.com/v1/leis/uploadComments"},"status":"Bad Request","code":400,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\r\n \"orderStatus\": \"invalid_request\",\r\n \"message\": \" Invalid Tracking Code - please contact our support team quoting your order tracking code, which can be found in the GUI interface, by clicking on the ‘Enhanced Detail’ from the LEI list. \",\r\n \"errorUri\": \"https://rapidlei.com/api\"\r\n}"}],"_postman_id":"42981c33-cec9-41ff-93bb-3e71c7e9aae1"},{"name":"LEI – Renew LEI","id":"b172b478-3fc2-49d9-a74d-cbb04880af0e","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.
\n","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity.
\n","key":"Content-Type","name":"Content-Type","type":"text","value":"application/json"}],"body":{"mode":"raw","raw":"{\r\n \"leiNumber\": \"98450024FD4543302F20\",\r\n \"isLevel1DataSame\": true,\r\n \"notificationUrl\": \"https://www.someotherserver.com/notify/me/when/lei/is/ready\",\r\n \"notificationToken\": \"Sq31YkqGWKXGEpeJGZwM\"\r\n}","options":{"raw":{"language":"json"}}},"url":"https://api.rapidlei.com/v1/leis/orders/renew","description":"This API endpoint initiates the workflow process to move the ‘nextRenewalDate’ forward by 1 year. Renewal is defined as the process to verify all Level 1 & Level 2 data remains accurate on an annual basis. All LEIs not in the final year of a contract will automatically attempt renewal. Only during the last 60 days of the final year of the contract may the contract for an LEI be renewed using this API endpoint. A full list of LEIs can be obtained using the “LEI – Query Renewable LEIs” endpoint. Note that LEIs cannot be renewed unless they have either LAPSED (i.e. outside of any contract) or they are in an ISSUED state and have a ‘nextRenewalDate’ which falls within 60 days of the renewal API call.
\nleiNumberLEI Number for the Legal Entity. e.g. 98450024FD4543302F20
\nisLevel1DataSame
A Boolean value – to agree that the current LE-RD (Level 1) data is the same as the previous year. LE-RD (Level 1 data for any LEI under the management of RapidLEI can be verified using the ‘Query Level 1 LE-RD and Authorised Representative’ endpoint
notificationUrlTo avoid unnecessary polling, webhooks can be used to pass orderStatus information in real time. A webhook is a user-defined HTTP (ideally HTTPS) endpoints which can accept POST requests for real time synchronous LEI processing. An optional security token may be used to avoid replay attacks, however the notificationUrl may also contain additional URL parameters. Webhook ApS in Denmark, ran by Simon Fredsted, offers a very simple listening service for testing webhooks. Please see https://webhook.site/ for details and usage guidelines. The two parameters returned in the RequestBody are - orderTrackingCode and orderStatus, with the optional security token being returned as notificationTokene.g. https://www.someotherserver.com/notify/me/when/lei/is/ready
or https://www.someotherserver.com/notify/me/when/lei/is/ready?type=exampletype&token=URL_based_token_examplePLEASE NOTE - Redirects are not guaranteed to be supported in all cases therefore please ensure the correct URL and any final / characters in the URL are sent.
notificationTokenAn optional unique token to avoid the possibility of a third party accidentally making a call to a static notification URL and therefore maliciously affecting the workflow.
e.g. Sq31YkqGWKXGEpeJGZwM\"
userCommentsAn optional comment or instruction to aid efficient processing of the LEI by the RapidLEI vetting team – to be used primarily for simple comments < 1000 characters to avoid the need to send additional corroborating documents.
\nfirstNameThe First Name(s) of the Authorised Representative with the responsibility/authority to request and approve the creation of an LEI e.g. Peter. Only send this if the signing authority has changed in the last year.
\nlastNameThe Last Name of the Authorised Representative e.g. Anderson. Only send this if the signing authority has changed in the last year.
\nmultiYearSupportAn integer from 1 to 5. Please see https://rapidlei.com/lei-pricing/ for details. Please default to 1 as the standard option.
\nloaFile
\nA Letter of Authorization (LoA) is used to provide linkage between the Applicant applying for the LEI and the empowered Authorised Representative name submitted as firstName lastName parameters. LoA's are optional as they can be replaced with appropriate Terms & Conditions. It is usual for a Registration Agent to provide T's and C's which negate the need for an LoA, however, in lieu of these being available, an LoA would be required to provide permission to the Registration Agent from the Empowered Authorised Representative. For more details please discuss with our legal team legal(a)rapidlei.com. Only 1 LoA may be submitted using either the fileData method or fileUrl method.
\ncorroboratingFiles
Up to 10 additional files which may aid vetting or validation of the Application. Please note the upload limit of 20MB each.
The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.
\n","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"key":"Content-Type","value":"application/json","description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity.
\n","type":"text"}],"url":"https://api.rapidlei.com/v1/lei/orders/{orderTrackingCode}/status","description":"This API endpoint is used to check the LEI orderStatus. The bearer access Token from 'Authentication - Request Access Token' is required to submit the request and a valid 'orderTrackingCode' must be submitted within in the URL.
\nfailure\n Sent when unable to process the requested action. See message for additional details as responses vary dependent on the workflow.
\nsuccess\n Sent when actionable. Additional responses dependent on the workflow. e.g. orderTrackingCode & confidenceLevel sent in response to a successful 'New LEI' request.
\nin_progress\n The order is with RapidLEI to progress (gather data, confirm information etc)
\nstopped\n No further action can take place.
\ncomplete\n The workflow is complete. Additional responses dependent on the workflow. e.g. \"message\" & \"leiCode\" returned in response to a successfully issued, imported or renewed LEI
\npending\n LEI Confirm LE-RD Data Quality required by API
\npending_gui\n Confirmation required or additional information required – only possible via the GUI interface
\ninvalid_request\n This message is returned when mandatory parameters are missing
\nauthorization_error\n This message is returned if there's a failure due to either an invalid client_id (email address) or client_secret (API key from My Settings)
\nnot_found\n This message is returned if there's an error in the requested URL
\nunsupported_grant_type\n This message is returned when the underlying protocol for bearer tokens is not used correctly.
\nserver_error\n This message is returned when there is an unexpected issue with the workflow or permission as opposed to a missing parameter
\nThe Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.
\n","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity.
\n","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://api.rapidlei.com/v1/lei/orders/{orderTrackingCode}/confirmation/{orderConfirmationStatus}","description":"This API call is used to confirm the LE-RD data quality status before an LEI can be issued. Set the correct 'orderTrackingCode' in the URL before making an API call. Also make sure you are passing either true or false while replacing the 'orderConfirmationStatus' parameter in the URL.
\nThis API call is one of the most important calls. The call is used to confirm the acceptance of the LE-RD (Legal Entity Reference Data) returned through the 'LEI - Check LEI Order status'. A Legal Entity must be presented with the LE-RD and MUST confirm the accuracy of the data. The Access Token from 'Authentication - Request Access Token' is required to submit the request and the acceptance by the Legal Entity is either 'True' - i.e. The Legal Entity agrees to and accepts the LE-RD or 'False' - i.e. There is an error which must be corrected. It is suggested that a feedback form is used to obtain details of the error. Submitting 'False' requires follow up via the RapidLEI Identity Platform GUI. Submitting 'True' requires the use of the 'LEI - Check LEI Order Status' to obtain the LEI Number.
\n","urlObject":{"protocol":"https","path":["v1","lei","orders","{orderTrackingCode}","confirmation","{orderConfirmationStatus}"],"host":["api","rapidlei","com"],"query":[],"variable":[]}},"response":[{"id":"b54c1c22-f6ef-4953-b6f4-d4a5770cbc31","name":"Successful Response - Data Quality Confirmation ‘false’","originalRequest":{"method":"POST","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"}],"url":"https://api.rapidlei.com/v1/lei/orders/987a9sd8f7a9sd8f7/confirmation/false"},"status":"OK","code":200,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderTrackingCode\": \"987a9sd8f7a9sd8f7\",\n \"orderStatus\": \"stopped\",\n \"message\": \"We have received confirmation of DISAGREEMENT to the LE-RD Data Quality. We are unable to continue processing this order using the API - Please login to the RapidLEI Identity Platform to continue the process via the ‘Pending’ filter.\"\n}"},{"id":"41a69477-c12c-4251-b676-c72e0f765e3e","name":"Successful Response - Data Quality confirmation ‘true’ (Import LEI)","originalRequest":{"method":"POST","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"}],"url":"https://api.rapidlei.com/v1/lei/orders/987a9sd8f7a9sd8f7/confirmation/true"},"status":"OK","code":200,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderTrackingCode\": \"987a9sd8f7a9sd8f7\",\n \"orderStatus\": \"in_progress\",\n \"message\": \"We have received confirmation of AGREEMENT to the LE-RD Data Quality and will continue processing your order. Your LEI will be imported shortly.\"\n}"},{"id":"43437195-bc16-4ce1-9448-d744a7e0151f","name":"Successful Response - Data Quality confirmation ‘true’ (New LEI)","originalRequest":{"method":"PUT","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"key":"Content-Type","value":"application/json","description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","type":"text"}],"url":"https://api.rapidlei.com/v1/lei/orders/987a9sd8f7a9sd8f7/confirmation/true"},"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderTrackingCode\": \"987a9sd8f7a9sd8f7\",\n \"orderStatus\": \"in_progress\",\n \"message\": \"We have received confirmation of AGREEMENT to the LE-RD Data Quality and will continue processing your order. Your LEI will be imported shortly.\"\n}"},{"id":"297480d0-8448-4ec4-aa1b-c86227668278","name":"Unsuccessful Response - LE-RD Data Quality Confirmation already received and processed","originalRequest":{"method":"POST","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"}],"url":"https://api.rapidlei.com/v1/lei/orders/987a9sd8f7a9sd8f7/confirmation/true"},"status":"Internal Server Error","code":500,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\r\n \"orderTrackingCode\": \"987a9sd8f7a9sd8f7\",\r\n \"orderStatus\": \"failure\",\r\n \"message\": \"We've already received the LE-RD confirmation from you for this Legal Entity - if in doubt, please contact our support team quoting your order tracking code, which can be found in the GUI interface, by clicking on the ‘Enhanced Detail’ from the LEI list.\"\r\n}"},{"id":"775a389b-0186-4720-8729-d757842b9d57","name":"Unsuccessful Response - InComplete Company Profile Loaded","originalRequest":{"method":"PUT","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"key":"Content-Type","value":"application/json","description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","type":"text"}],"url":"https://api.rapidlei.com/v1/lei/orders/987a9sd8f7a9sd8f7/confirmation/true"},"status":"Internal Server Error","code":500,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderTrackingCode\": \"987a9sd8f7a9sd8f7\",\n \"orderStatus\": \"failure\",\n \"message\": \"We have been unable to obtain all data from the business registry, so we are unable to continue processing using the API. Please login to the RapidLEI Identity Platform to continue the process.\"\n}"},{"id":"42bff25f-d16c-48ef-8b19-b4fc436a3bdb","name":"Unsuccessful Response - Company Profile Not Loaded","originalRequest":{"method":"PUT","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"key":"Content-Type","value":"application/json","description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","type":"text"}],"url":"https://api.rapidlei.com/v1/lei/orders/987a9sd8f7a9sd8f7/confirmation/true"},"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\r\n \"orderTrackingCode\": \"987a9sd8f7a9sd8f7\",\r\n \"orderStatus\": \"failure\",\r\n \"message\": \"Operation not allowed. Please use the Check Order Status API.\"\r\n}"},{"id":"3f676d32-5464-46db-b253-dafb49f8ba9b","name":"Unsuccessful Response - 'orderConfirmationStatus' must be true or false","originalRequest":{"method":"POST","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"}],"url":"https://api.rapidlei.com/v1/lei/orders/987a9sd8f7a9sd8f7/confirmation/asdf"},"status":"Bad Request","code":400,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderStatus\": \"invalid_request\",\n \"message\": \"Request parameter 'orderConfirmationStatus' should contain a Boolean value of either 'true' or 'false'\",\n \"errorUri\": \"https://rapidlei.com/api\"\n}"},{"id":"cb50629c-ae32-49d6-b626-cb31113421ff","name":"Unsuccessful Response - Unknown error OR Exception during processing request","originalRequest":{"method":"POST","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"}],"url":"https://api.rapidlei.com/v1/lei/orders/987a9sd8f7a9sd8f7/confirmation/true"},"status":"Internal Server Error","code":500,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderStatus\": \"server_error\",\n \"message\": \"We've been unable to process your request - please contact our support team quoting your order tracking code, which can be found in the GUI interface, by clicking on the ‘Enhanced Detail’ from the LEI list.\",\n \"errorUri\": \"https://rapidlei.com/api\"\n}"},{"id":"76c46e02-d6b8-47cd-be8c-c5156b015c0d","name":"Successful Response – Data Quality Pre–Check and Duplicate API calls are being made to the GLEIS for new LEIs","originalRequest":{"method":"POST","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"}],"url":"https://api.rapidlei.com/v1/lei/orders/987a9sd8f7a9sd8f7/confirmation/true"},"status":"OK","code":200,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\r\n \"orderTrackingCode\": \"987a9sd8f7a9sd8f7\",\r\n \"orderStatus\": \"in_progress\",\r\n \"message\": \" You've submitted the Data Duality Confirmation at the point we are doing a Check for Duplicates (C4D) call to the GLEIS. These can take between 15 and 45 seconds. We've acknowledged your confirmation of the profile accuracy, so you do not need to submit again.\"\r\n}"},{"id":"83acbcf8-6472-4ba7-acb4-a4b786c52eab","name":"Successful Response – Data Quality Pre–Check calls are being made to the GLEIS for imported LEIs","originalRequest":{"method":"POST","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"}],"url":"https://api.rapidlei.com/v1/lei/orders/987a9sd8f7a9sd8f7/confirmation/true"},"status":"OK","code":200,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\r\n \"orderTrackingCode\": \"987a9sd8f7a9sd8f7\",\r\n \"orderStatus\": \"in_progress\",\r\n \"message\": \" You've submitted the Data Duality Confirmation at the point we are doing a Check for Duplicates (C4D) call to the GLEIS. These can take between 15 and 45 seconds. We've acknowledged your confirmation of the profile accuracy, so you do not need to submit again.\"\r\n}"}],"_postman_id":"7beec4fe-ab4d-48b5-a4eb-5886ecdd64f1"},{"name":"LEI - Query all LEIs","id":"856cf8ab-3611-47c7-95f5-e3280ba0e48e","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"GET","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.
\n","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity.
\n","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://api.rapidlei.com/v1/leis/orders","description":"This API is used to query for a list of ALL LEIs which have been successfully issued (Created or Imported) from the account. This includes shopping cart and XLS based bulk workflows. Any LEI which has not yet been issued, but has been created by API calls can be verified individually by the 'LEI - Check Order Status' call. Any requests made via the shopping cart or xls methods may be tracked from within the browser based UI by logging in to the https://lei.rapidlei.com/Account/Login. The Access Token from 'Authentication - Request Access Token' is required to submit the request.
\nPlease note that this API call DOES NOT return LEI numbers if the LEI has been marked as a DUPLICATE, ANULLED, MERGED or RETIRED.
\nOnly LEIs with a registration status of ISSUED or LAPSED will be returned.
\nReviewing LEI-RD (Reference data) is possible via the LEI number and the GLEIF API call. https://www.gleif.org/en/lei-data/gleif-lei-look-up-api/access-the-api
\n","urlObject":{"protocol":"https","path":["v1","leis","orders"],"host":["api","rapidlei","com"],"query":[],"variable":[]}},"response":[{"id":"399e028c-29c8-4464-b012-fb321c014568","name":"Successful Response – List of LEIs returned","originalRequest":{"method":"GET","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://api.rapidlei.com/v1/leis/orders"},"status":"OK","code":200,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\r\n \"new\": [\r\n \"984500049401E2B8D492\",\r\n \"984500049401E2B8D491\",\r\n \"984500049401E2B8D494\"\r\n ],\r\n \"imported\": [\r\n \"213800MAKC4IOK7LEH11\",\r\n \"213800MAKC4IOK7LEH12\",\r\n \"213800MAKC4IOK7LEH13\"\r\n ]\r\n}"},{"id":"b75ebf73-35ba-47e9-84c5-385fa7cea16c","name":"Unsuccessful Response – Unknown Error or Exception during processing request","originalRequest":{"method":"GET","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://api.rapidlei.com/v1/leis/orders"},"status":"Internal Server Error","code":500,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderStatus\": \"server_error\",\n \"message\": \" We've been unable to process your request – please contact our support team.\",\n \"errorUri\": \"https://rapidlei.com/api\"\n}"},{"id":"af1da67f-3c1a-4275-80bf-69a4a26acc4d","name":"Unsuccessful Response – User not allowed to use the Full API, only the ‘Create User’ endpoint","originalRequest":{"method":"GET","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://api.rapidlei.com/v1/leis/orders"},"status":"Unauthorized","code":401,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderStatus\": \"authorization_error\",\n \"message\": \"You do not have the ability to use the Full RapidLEI API from this account – you are configured only to use the ‘Create User’ endpoint, please contact our support team on support@rapidlei.com\",\n \"errorUri\": \"https://rapidlei.com/api\"\n}"}],"_postman_id":"856cf8ab-3611-47c7-95f5-e3280ba0e48e"},{"name":"LEI – Query Lapsed LEIs","id":"9746e52f-0935-4c8e-8e39-784e4c061ec5","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"GET","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.
\n","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity.
\n","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://api.rapidlei.com/v1/leis/orders/lapsed","description":"This API call is used to query all LAPSED LEIs.
\n","urlObject":{"protocol":"https","path":["v1","leis","orders","lapsed"],"host":["api","rapidlei","com"],"query":[],"variable":[]}},"response":[{"id":"ae96460f-4e69-4af8-8358-f12c86bd0711","name":"Successful Response – List of LEIs and nextRenewalDate’s returned","originalRequest":{"method":"GET","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://api.rapidlei.com/v1/leis/orders/lapsed"},"status":"OK","code":200,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"[\n {\n \"leiNumber\": \"14955838975411027285\",\n \"nextRenewalDate\": \"2021-07-09T11:54:35+00:00\"\n },\n {\n \"leiNumber\": \"984500EFP7C0E4CEA733\",\n \"nextRenewalDate\": \"2021-07-29T11:54:35+00:00\"\n },\n {\n \"leiNumber\": \"984500801560A0481F75\",\n \"nextRenewalDate\": \"2021-07-09T11:54:35+00:00\"\n }\n]"},{"id":"99fa20db-26b1-4a96-9fc3-7b1187e2ce1a","name":"Unsuccessful Response – User not allowed to use the Full API, only the ‘Create User’ endpoint","originalRequest":{"method":"GET","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://api.rapidlei.com/v1/leis/orders/lapsed"},"status":"Unauthorized","code":401,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderStatus\": \"authorization_error\",\n \"message\": \"You do not have the ability to use the Full RapidLEI API from this account – you are configured only to use the ‘Create User’ endpoint, please contact our support team on support@rapidlei.com\",\n \"errorUri\": \"https://rapidlei.com/api\"\n}"},{"id":"4af1b10c-7f07-4714-8e8b-6e9182812d39","name":"Unsuccessful Response – Unknown Error or Exception during processing request","originalRequest":{"method":"GET","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://api.rapidlei.com/v1/leis/orders/lapsed"},"status":"Internal Server Error","code":500,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderStatus\": \"server_error\",\n \"message\": \" We've been unable to process your request - please contact our support team.\",\n \"errorUri\": \"https://rapidlei.com/api\"\n}"}],"_postman_id":"9746e52f-0935-4c8e-8e39-784e4c061ec5"},{"name":"LEI – Query Renewable LEIs","id":"90ff94a9-fde0-47bb-bf99-a4c19d30d1e7","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"GET","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.
\n","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity.
\n","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://api.rapidlei.com/v1/leis/orders/renew/{days}","description":"This API call is used to query all LEIs which may be renewed within the next {days}. The parameter \"days\" is a numeric value between 1 and 60. Ideally values of 15, 30, 45 or 60 are passed to mirror the GUI DASHBOARD Interface. Please note that multi-year LEIs will automatically renew 60 days prior to the “nextRenewalDate” and are therefore excluded from the returned list. The exception being any LEI with Level 2 data or any ESO based FUND which cannot be verified by the RapidLEI vetting team - these will appear too.
\n","urlObject":{"protocol":"https","path":["v1","leis","orders","renew","{days}"],"host":["api","rapidlei","com"],"query":[],"variable":[]}},"response":[{"id":"2edaa3ec-e1fd-491d-aad7-ab1e66282c94","name":"Successful Response – List of LEIs and nextRenewalDate’s returned","originalRequest":{"method":"GET","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://api.rapidlei.com/v1/leis/orders/renew/60"},"status":"OK","code":200,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"[\n {\n \"leiNumber\": \"14955838975411027285\",\n \"nextRenewalDate\": \"2021-07-09T11:54:35+00:00\"\n },\n {\n \"leiNumber\": \"984500EFP7C0E4CEA733\",\n \"nextRenewalDate\": \"2021-07-29T11:54:35+00:00\"\n },\n {\n \"leiNumber\": \"984500801560A0481F75\",\n \"nextRenewalDate\": \"2021-07-09T11:54:35+00:00\"\n }\n]"},{"id":"01262285-74f5-49ec-ad07-04d948074ca1","name":"Unsuccessful Response – User not allowed to use the Full API, only the ‘Create User’ endpoint","originalRequest":{"method":"GET","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://api.rapidlei.com/v1/leis/orders/renew/60"},"status":"Unauthorized","code":401,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderStatus\": \"authorization_error\",\n \"message\": \"You do not have the ability to use the Full RapidLEI API from this account – you are configured only to use the ‘Create User’ endpoint, please contact our support team on support@rapidlei.com\",\n \"errorUri\": \"https://rapidlei.com/api\"\n}"},{"id":"a3359c3a-a2ae-4bde-ae0b-d28b4ad3ca59","name":"Unsuccessful Response – Unknown Error or Exception during processing request","originalRequest":{"method":"GET","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://api.rapidlei.com/v1/leis/orders/renew/60"},"status":"Internal Server Error","code":500,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderStatus\": \"server_error\",\n \"message\": \" We've been unable to process your request - please contact our support team.\",\n \"errorUri\": \"https://rapidlei.com/api\"\n}"},{"id":"3b053889-68a3-405e-9c2e-707b2675d0de","name":"Unsuccessful Response – Invalid or nonnumeric days parameter","originalRequest":{"method":"GET","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://api.rapidlei.com/v1/leis/orders/renew/100"},"status":"Bad Request","code":400,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderStatus\": \"invalid_request\",\n \"message\": \"Request parameter ‘days’ should contain a numeric value between 1 and 60\",\n \"errorUri\": \"https://rapidlei.com/api\"\n}"}],"_postman_id":"90ff94a9-fde0-47bb-bf99-a4c19d30d1e7"},{"name":"LEI – Query Level 1 LE-RD and Authorised Representative","id":"66085790-36f3-4221-a240-cb495b55b7cc","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"GET","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.
\n","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity.
\n","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://api.rapidlei.com/v1/leis/level1/{leiNumber}","description":"This API call is used to query Level 1 (LE-RD) data for any LEI managed by RapidLEI
\n","urlObject":{"protocol":"https","path":["v1","leis","level1","{leiNumber}"],"host":["api","rapidlei","com"],"query":[],"variable":[]}},"response":[{"id":"e560c873-87f5-44d0-92fa-4a39639042f6","name":"Successful Response – LEI Level 1 LE-RD and Authorised Representative data available","originalRequest":{"method":"GET","header":[{"key":"Authorization","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx","description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","type":"text"},{"key":"Content-Type","value":"application/json","description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","type":"text"}],"url":"https://api.rapidlei.com/v1/leis/level1/529900T8BM49AURSDO55"},"status":"OK","code":200,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"signingAuthorityName\": \"Paul Tourret\",\n \"referenceData\": {\n \"leiNumber\": \"529900T8BM49AURSDO55\",\n \"legalName\": \"Ubisecure Oy\",\n \"legalNameLanguage\": \"fi\",\n \"registrationAuthorityEntityId\": \"1748721–4\",\n \"entityLegalFormCode\": \"DKUW\",\n \"entityLegalForm\": null,\n \"entityLegalFormLanguage\": \"FI\",\n \"entityStatus\": \"ACTIVE\",\n \"registrationAuthorityId\": \"RA000188\",\n \"registrationAuthority\": null,\n \"entityCategory\": \"GENERAL\",\n \"entityCreationDate\" : \"2002-02-14T00:00:00+00:00\",\n \"legalJurisdiction\": \"FI\",\n \"initialRegistrationDate\": \"2016–08–04T11:00:36+00:00\",\n \"nextRenewalDate\": \"2025–12–20T12:23:13+00:00\",\n \"lastUpdateDate\": \"2024–12–20T12:23:13+00:00\",\n \"registrationStatus\": \"ISSUED\",\n \"validationSource\": \"FULLY_CORROBORATED\",\n \"managingLOU\": \"529900T8BM49AURSDO55\",\n \"successorLEI\": null,\n \"successorEntityName\": null,\n \"contractExpiryDate\": \"2028-01-21T21:54:37+00:00\",\n \"otherEntityNames\": [\n {\n \"type\": \"TRADING_OR_OPERATING_NAME\",\n \"value\": \"Ubisecure Inc\",\n \"language\": \"FI\"\n },\n {\n \"type\": \"TRADING_OR_OPERATING_NAME\",\n \"value\": \"Ubisecure Ab\",\n \"language\": \"SV\"\n }\n ],\n \"transliteratedOtherEntityNames\": [],\n \"legalAddress\": {\n \"mailRouting\": null,\n \"firstAddressLine\": \"Vaisalantie 2\",\n \"addressLine1\": null,\n \"addressLine2\": null,\n \"addressLine3\": null,\n \"city\": \"Espoo\",\n \"state\": null,\n \"country\": \"FI\",\n \"postalCode\": \"02130\"\n },\n \"transliertatedLegalAddress\": null,\n \"headquartersAddress\": {\n \"mailRouting\": null,\n \"firstAddressLine\": \"Tekniikantie 14\",\n \"addressLine1\": null,\n \"addressLine2\": null,\n \"addressLine3\": null,\n \"city\": \"Espoo\",\n \"state\": null,\n \"country\": \"FI\",\n \"postalCode\": \"02150\"\n },\n \"transliteratedHeadquartersAddress\": null,\n \"validationAuthority\": {\n \"validationAuthorityID\": \"RA000188\",\n \"otherValidationAuthorityID\": null,\n \"validationAuthorityEntityID\": \"1748721–4\"\n },\n \"otherValidationAuthorities\": []\n }\n} "},{"id":"8c7cda61-9e8d-4981-bd16-7f57332a1369","name":"Unsuccessful Response – LEI not managed by your RapidLEI account","originalRequest":{"method":"GET","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://api.rapidlei.com/v1/leis/level1/529900T8BM49AURSDO55"},"status":"Internal Server Error","code":500,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderStatus\": \"failure\",\n \"message\": \"The LEI number requested is not managed by your RapidLEI account. Please provide a valid LEI Number or contact our support team to discuss options.\"\n}"},{"id":"51b88e2f-4c21-4a4a-92eb-47d4a9007080","name":"Unsuccessful Response – Level 1 data is not currently available","originalRequest":{"method":"GET","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://api.rapidlei.com/v1/leis/level1/529900T8BM49AURSDO55"},"status":"Internal Server Error","code":500,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderStatus\": \"failure\",\n \"message\": \" The LEI must be either ISSUED, LASPED, DUPLICATE, PENDING_TRANSFER, PENDING_ARCHIVAL, RETIRED or MERGED for level 1 data to be available. LEIs which are ‘pending’, ‘pending_gui’ or ‘in_progress’ may not be queried.\"\n}"},{"id":"89f06fb0-f9a2-4859-9e3d-c935f5f75761","name":"Unsuccessful Response – Invalid LEI Format","originalRequest":{"method":"GET","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://api.rapidlei.com/v1/leis/level1/529900T8BM49A"},"status":"Bad Request","code":400,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderStatus\": \"invalid_request\",\n \"message\": \"Please ensure the 'lei' is a valid ISO 17442 format LEI (20 characters).\",\n \"errorUri\": \"https://rapidlei.com/api\"\n}"},{"id":"abacaf04-4f0b-4d67-a3b2-d4b943a74944","name":"Unsuccessful Response – User not allowed to use the Full API, only the ‘Create User’ endpoint","originalRequest":{"method":"GET","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://api.rapidlei.com/v1/leis/level1/529900T8BM49AURSDO55"},"status":"Unauthorized","code":401,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderStatus\": \"authorization_error\",\n \"message\": \"You do not have the ability to use the Full RapidLEI API from this account – you are configured only to use the ‘Create User’ endpoint, please contact our support team on support@rapidlei.com\",\n \"errorUri\": \"https://rapidlei.com/api\"\n}"},{"id":"53e023f3-eba1-42f9-9a36-b8f113026240","name":"Unsuccessful Response – Unknown Error or Exception during processing request","originalRequest":{"method":"GET","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://api.rapidlei.com/v1/leis/level1/529900T8BM49AURSDO55"},"status":"Internal Server Error","code":500,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderStatus\": \"server_error\",\n \"message\": \" We've been unable to process your request - please contact our support team.\",\n \"errorUri\": \"https://rapidlei.com/api\"\n}"}],"_postman_id":"66085790-36f3-4221-a240-cb495b55b7cc"},{"name":"LEI – Query Level 2 LE-RR, LE-RE and PNI data","id":"1fceda6c-5bd7-4a33-9325-008c851267e9","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"GET","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.
\n","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity.
\n","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://api.rapidlei.com/v1/leis/level2/{leiNumber}","description":"This API call is used to query Level 2 (LE-RR) data for any LEI managed by RapidLEI. This includes, relationship data, exception reporting and if level 2 parents do not have LEIs, PNI data.
\n","urlObject":{"protocol":"https","path":["v1","leis","level2","{leiNumber}"],"host":["api","rapidlei","com"],"query":[],"variable":[]}},"response":[{"id":"ddeaf619-e3b6-472a-8602-b379ce7b90ff","name":"Successful Response – Level 2 data has Reporting Exceptions ","originalRequest":{"method":"GET","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://api.rapidlei.com/v1/leis/level2/984500B8IBDAB46C3750"},"status":"OK","code":200,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"relationshipRecords\": [],\n \"reportingExceptions\": [\n {\n \"lei\": \"984500B8IBDAB46C3750\",\n \"exceptionCategory\": \"DIRECT_ACCOUNTING_CONSOLIDATION_PARENT\",\n \"exceptionReason\": \"NATURAL_PERSONS\",\n \"exceptionReference\": null\n },\n {\n \"lei\": \"984500B8IBDAB46C3750\",\n \"exceptionCategory\": \"ULTIMATE_ACCOUNTING_CONSOLIDATION_PARENT\",\n \"exceptionReason\": \"NATURAL_PERSONS\",\n \"exceptionReference\": null\n }\n ],\n \"parentReferenceRecords\": []\n}"},{"id":"d0e787cf-61f3-4679-893e-bfb47930c115","name":"Successful Response – Level 2 data has Relationship Records","originalRequest":{"method":"GET","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://api.rapidlei.com/v1/leis/level2/984500B8IBDAB46C3750"},"status":"OK","code":200,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"relationshipRecords\": [\n {\n \"startNode\": {\n \"nodeID\": \"529900T8BM49AURSDO55\",\n \"nodeIDType\": \"LEI\"\n },\n \"endNode\": {\n \"nodeID\": \"89450051ZRDOL9KEWH63\",\n \"nodeIDType\": \"LEI\"\n },\n \"relationshipType\": \"IS_DIRECTLY_CONSOLIDATED_BY\",\n \"relationshipStatus\": \"ACTIVE\",\n \"initialRegistrationDate\": \"2018-05-08T18:15:52+00:00\",\n \"lastUpdateDate\": \"2021-02-20T12:23:13+00:00\",\n \"nextRenewalDate\": \"2022-12-20T12:23:13+00:00\",\n \"registrationStatus\": \"PUBLISHED\",\n \"managingLOU\": \"529900T8BM49AURSDO55\",\n \"validationSources\": \"FULLY_CORROBORATED\",\n \"validationDocuments\": \"ACCOUNTS_FILING\",\n \"validationReference\": null,\n \"relationshipQualifier\": {\n \"qualifierDimension\": \"ACCOUNTING_STANDARD\",\n \"qualifierCategory\": \"OTHER_ACCOUNTING_STANDARD\"\n },\n \"relationshipQuantifier\": {\n \"measurementMethod\": \"ACCOUNTING_CONSOLIDATION\",\n \"quantifierAmount\": 100,\n \"quantifierUnits\": \"PERCENTAGE\"\n },\n \"relationshipPeriods\": [\n {\n \"startDate\": \"2021-01-01T00:00:00+00:00\",\n \"endDate\": \"2021-12-31T00:00:00+00:00\",\n \"periodType\": \"ACCOUNTING_PERIOD\"\n },\n {\n \"startDate\": \"2018-05-17T00:00:00+00:00\",\n \"endDate\": null,\n \"periodType\": \"RELATIONSHIP_PERIOD\"\n }\n ]\n },\n {\n \"startNode\": {\n \"nodeID\": \"529900T8BM49AURSDO55\",\n \"nodeIDType\": \"LEI\"\n },\n \"endNode\": {\n \"nodeID\": \"89450051ZRDOL9KEWH63\",\n \"nodeIDType\": \"LEI\"\n },\n \"relationshipType\": \"IS_ULTIMATELY_CONSOLIDATED_BY\",\n \"relationshipStatus\": \"ACTIVE\",\n \"initialRegistrationDate\": \"2018-05-08T18:15:52+00:00\",\n \"lastUpdateDate\": \"2021-02-20T12:23:13+00:00\",\n \"nextRenewalDate\": \"2022-12-20T12:23:13+00:00\",\n \"registrationStatus\": \"PUBLISHED\",\n \"managingLOU\": \"529900T8BM49AURSDO55\",\n \"validationSources\": \"FULLY_CORROBORATED\",\n \"validationDocuments\": \"ACCOUNTS_FILING\",\n \"validationReference\": null,\n \"relationshipQualifier\": {\n \"qualifierDimension\": \"ACCOUNTING_STANDARD\",\n \"qualifierCategory\": \"OTHER_ACCOUNTING_STANDARD\"\n },\n \"relationshipQuantifier\": {\n \"measurementMethod\": \"ACCOUNTING_CONSOLIDATION\",\n \"quantifierAmount\": 100,\n \"quantifierUnits\": \"PERCENTAGE\"\n },\n \"relationshipPeriods\": [\n {\n \"startDate\": \"2021-01-01T00:00:00+00:00\",\n \"endDate\": \"2021-12-31T00:00:00+00:00\",\n \"periodType\": \"ACCOUNTING_PERIOD\"\n },\n {\n \"startDate\": \"2018-05-17T00:00:00+00:00\",\n \"endDate\": null,\n \"periodType\": \"RELATIONSHIP_PERIOD\"\n }\n ]\n }\n ],\n \"reportingExceptions\": [],\n \"parentReferenceRecords\": []\n}"},{"id":"e8c955fb-6a56-43d4-8212-c08342251ec2","name":"Successful Response – Level 2 data has Parent Reference Data (PNI) ","originalRequest":{"method":"GET","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://api.rapidlei.com/v1/leis/level2/984500B8IBDAB46C3750"},"status":"OK","code":200,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"relationshipRecords\": [],\n \"reportingExceptions\": [\n {\n \"lei\": \"984500B8IBDAB46C3750\",\n \"exceptionCategory\": \"DIRECT_ACCOUNTING_CONSOLIDATION_PARENT\",\n \"exceptionReason\": \"NO_LEI\",\n \"exceptionReference\": null\n },\n {\n \"lei\": \"984500B8IBDAB46C3750\",\n \"exceptionCategory\": \"ULTIMATE_ACCOUNTING_CONSOLIDATION_PARENT\",\n \"exceptionReason\": \"NO_LEI\",\n \"exceptionReference\": null\n }\n ],\n \"parentReferenceRecords\": [\n {\n \"legalName\": \"UBISECURE HOLDINGS LIMITED\",\n \"registrationAuthorityEntityId\": \"10408185\",\n \"legalJurisdiction\": \"GB–ENG\",\n \"parentType\": \"DIRECT_PARENT\"\n },\n {\n \"legalName\": \"UBISECURE HOLDINGS LIMITED\",\n \"legalNameLanguage\": \"en\",\n \"registrationAuthorityEntityId\": \"10408185\",\n \"legalJurisdiction\": \"GB–ENG\",\n \"parentType\": \"ULTIMATE_PARENT\"\n }\n ]\n}"},{"id":"873b297a-4353-4af6-bcef-b3787ecb926a","name":"Successful Response – Level 2 Fund Reporting","originalRequest":{"method":"GET","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://api.rapidlei.com/v1/leis/level2/984500B8IBDAB46C3750"},"status":"OK","code":200,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"relationshipRecords\": [\n {\n \"startNode\": {\n \"nodeID\": \"529900T8BM49AURSDO55\",\n \"nodeIDType\": \"LEI\"\n },\n \"endNode\": {\n \"nodeID\": \"89450051ZRDOL9KEWH63\",\n \"nodeIDType\": \"LEI\"\n },\n \"relationshipType\": \"IS_FEEDER_TO\",\n \"relationshipStatus\": \"ACTIVE\",\n \"initialRegistrationDate\": \"2021–12–20T12:23:13+00:00\",\n \"lastUpdateDate\": \"2021–12–20T12:23:13+00:00\",\n \"nextRenewalDate\": \"2022–12–20T12:23:13+00:00\",\n \"registrationStatus\": \"PUBLISHED\",\n \"managingLOU\": \"529900T8BM49AURSDO55\",\n \"validationSources\": \"ENTITY_SUPPLIED_ONLY\",\n \"validationDocuments\": \"ACCOUNTS_FILING\",\n \"validationReference\": \"https://www.fund-data-reference-example.com\",\n \"relationshipPeriods\": [\n {\n \"startDate\": \"2020-01-14T00:00:00+00:00\",\n \"endDate\": null,\n \"periodType\": \"RELATIONSHIP_PERIOD\"\n }\n ]\n }\n ],\n \"reportingExceptions\": [\n {\n \"lei\": \"529900T8BM49AURSDO55\",\n \"exceptionCategory\": \"DIRECT_ACCOUNTING_CONSOLIDATION_PARENT\",\n \"exceptionReason\": \"NON_CONSOLIDATING\",\n \"exceptionReference\": null\n },\n {\n \"lei\": \"529900T8BM49AURSDO55\",\n \"exceptionCategory\": \"ULTIMATE_ACCOUNTING_CONSOLIDATION_PARENT\",\n \"exceptionReason\": \"NON_CONSOLIDATING\",\n \"exceptionReference\": null\n }\n ],\n \"parentReferenceRecords\": []\n}"},{"id":"692d4c08-276c-4097-9e7c-51771d5b5688","name":"Unsuccessful Response – LEI not managed by your RapidLEI account","originalRequest":{"method":"GET","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://api.rapidlei.com/v1/leis/level2/984500B8IBDAB46C3750"},"status":"Internal Server Error","code":500,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderStatus\": \"failure\",\n \"message\": \"The LEI number requested is not managed by your RapidLEI account. Please provide a valid LEI Number or contact our support team to discuss options.\"\n}"},{"id":"6fa90fcf-a15f-4846-ba0c-8d202b5a4f2f","name":"Unsuccessful Response – Level 2 data is not currently available","originalRequest":{"method":"GET","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://api.rapidlei.com/v1/leis/level2/984500B8IBDAB46C3750"},"status":"Internal Server Error","code":500,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderStatus\": \"failure\",\n \"message\": \" The LEI must be either ISSUED, LASPED, DUPLICATE, PENDING_TRANSFER, PENDING_ARCHIVAL, RETIRED or MERGED for level 2 data to be available. LEIs which are ‘pending’, ‘pending_gui’ or ‘in_progress’ may not be queried.\"\n}"},{"id":"b929c573-2cb3-4017-b929-a3ee796e0190","name":"Unsuccessful Response – Invalid LEI Format","originalRequest":{"method":"GET","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://api.rapidlei.com/v1/leis/level2/984500B8"},"status":"Bad Request","code":400,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderStatus\": \"invalid_request\",\n \"message\": \"Please ensure the 'lei' is a valid ISO 17442 format LEI (20 characters).\",\n \"errorUri\": \"https://rapidlei.com/api\"\n}"},{"id":"44d7f92f-588b-40cc-a6a0-3c87255c76a7","name":"Unsuccessful Response – User not allowed to use the Full API, only the ‘Create User’ endpoint","originalRequest":{"method":"GET","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://api.rapidlei.com/v1/leis/level2/984500B8IBDAB46C3750"},"status":"Unauthorized","code":401,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderStatus\": \"authorization_error\",\n \"message\": \"You do not have the ability to use the Full RapidLEI API from this account – you are configured only to use the ‘Create User’ endpoint, please contact our support team on support@rapidlei.com\",\n \"errorUri\": \"https://rapidlei.com/api\"\n}"},{"id":"c622d611-db08-4170-8b73-772cc45d0494","name":"Unsuccessful Response – Unknown Error or Exception during processing request","originalRequest":{"method":"GET","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://api.rapidlei.com/v1/leis/level2/984500B8IBDAB46C3750"},"status":"Internal Server Error","code":500,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderStatus\": \"server_error\",\n \"message\": \" We've been unable to process your request - please contact our support team.\",\n \"errorUri\": \"https://rapidlei.com/api\"\n}"}],"_postman_id":"1fceda6c-5bd7-4a33-9325-008c851267e9"}],"id":"42641d8a-4578-4efb-ae9d-d819c8c83958","description":"Version - September 2025
\nRapidLEI API endpoints have been designed to facilitate efficient workflows enabling Registration Agents, Validation Agents, and Enterprise's to 'Create New LEIs', 'Import Existing LEIs' or 'Renew LEIs'.
\nWith the exception of 'API Health Check', which requires no Authentication, RFC 6750 OAuth 2.0 Bearer Token Authentication is used in all cases. API Key(s) used to create Bearer Token(s) via the 'Authentication - Request Access Token' endpoint are managed in 'My Settings' in RapidLEI accounts with extended privileges.
\nFor access credentials please speak to our team on partnerships@rapidlei.com
\nThese API(s) rely on access being granted to the RapidLEI Production platform. For access credentials please speak to our team on partnerships@rapidlei.com.
\nThe RapidLEI API is designed to avoid unnecessary polling. Whenever possible, please use the built-in 'Push Notifications' system (Details given below). Status updates, enabling polling logic workflow optimizations, are returned via the orderStatus token, whereas optional, human readable feedback from the vetting team on why an LEI order has paused is available from the adminMessage token e.g. *\"The Business Registry is currently offline – We are unable to continue processing this order until it reopens.\"*
\nin_progress
The order is with RapidLEI to progress (gather data, confirm information etc)
stopped
No further action can take place.
complete
The workflow is complete. Additional responses dependent on the workflow. e.g. \"message\" & \"leiCode\" returned in response to a successfully issued, imported or renewed LEI
pending
LEI Confirm LE-RD Data Quality required by API
pending_gui
Confirmation required or additional information required – only possible via the GUI interface
invalid_request
This message is returned when mandatory parameters are missing
authorization_error
This message is returned if there's a failure due to either an invalid client_id (email address) or client_secret (API key from My Settings)
not_found
This message is returned if there's an error in the requested URL
unsupported_grant_type
This message is returned when the underlying protocol for bearer tokens is not used correctly.
server_error
This message is returned when there is an unexpected issue with the workflow or permission as opposed to a missing parameter
Push Notifications, aka webhooks are *\"user-defined callbacks made with HTTP\"* (ideally HTTPS) endpoints which can accept POST requests. An optional security token may be used to avoid replay attacks, however the notificationUrl may also contain additional URL parameters. Webhook ApS in Denmark, ran by Simon Fredsted, offers a very simple listening service for testing webhooks. Please see https://webhook.site/ for details and usage guidelines.
The two parameters returned in the RequestBody are - orderTrackingCode and orderStatus, with the optional security token being returned as notificationToken within the Header.
profile_loaded
Sent as soon as our platform obtains the profile from the business registry. In the event of a failure, or an incomplete profile being received, our vetting team adds the missing items the registry did not provide and at this point we send profile_loaded. This can be minutes or hours depending on the jurisdiction/registry. Please use 'LEI - Check Order Status' to verify the profile's accuracy. Either verify the returned profile against data previously provided by the Applicant, or use this data to confirm the accuracy with the Applicant in a post processing workflow.
lei_issued
Sent once the LEI is ISSUED and all checks are complete including the Authority Check. (Please note that we do not send a notification for a ‘Pre-Authority LEI number’). Please use 'LEI - Check Order Status' to obtain the LEI number and the nextRenewalDate.
lei_imported
Sent once the LEI is IMPORTED and all checks are complete including the Authority Check. Please use 'LEI - Check Order Status' to obtain the LEI number and the nextRenewalDate.
lei_cancelled
Sent after a cancellation from either our Admin team or the GUI interface. (Cancellation by API is not supported)
lei_pending_gui
Sent once an edge case is identified and control is returned to the GUI Interface.
lei_duplicate_found
A potential Duplicate has been identified by a GLEIF API call and our team are investigating.
lei_pre_check_api
A pre–check API call to GLEIF has failed – RapidLEI will be investigating and correcting any issues.
lei_renewed
Sent once the LEI is renewed and all checks are complete. Please use 'LEI - Check Order Status' to obtain the LEI number and the nextRenewalDate.
lei_published
Sent once the LEI has been successfully uploaded to the GLEIS during one of the 10 daily publication cycles. For a new LEI, or changes to an existing LEI to be visible, additional time must be allowed for the GLEIF to process the data and publish to the Concatenated files, Golden Copy files & LEI Search 2.0 system – this ranges between 2 and 8 hours of our publication time.
lou_import_requested
Sent when the request to the SENDING LOU has been made. The SENDING_LOU, in response, should flip the GLEIF LEI Status from ISSUED/LASPED to PENDING_TRANSFER within 3 days indicating the request is received and that they are talking to their client.
lou_import_request_acknowledged
Sent when the GLEIF LEI Status flips to PENDING_TRANSFER. The SENDING_LOU then has 4 days to confirm the acceptance or rejection of the request.
lou_rejected
Sent after receiving a rejection from the SENDING LOU during transfer by a GLEIF LEI Status change back to LASPED/ISSUED.
lei_transferred
Sent after an LEI has successfully been transferred. i.e from RapidLEI (as the Sending LOU) to the Receiving LOU. This status will only appear when the Receiving LOU publishes the LEI to the GLEIS.
The maximum allowed FileName length (including an extension) = 250 characters e.g. \"FileName\":\"This is an example file name which shows the extent possible within the RapidLEI API eco system for Ubisecure Oy with LEI Code 529900T8BM49AURSDO55 - The remaining characters up to 250 being these... 4567890123456789012345678901234567890123456789.pdf”
\nThe maximum allowed FileURL length (including an extension) = 1000 characters e.g. \"FileURL\":\"https://someexamplefileserver.com/attachements/rapidlei/ BNVcyW5rbFdjYzAwekdONHhMU1hMbFBoWFV0bXBra2FuQ1dzUWVMYWoyRUJoU3huRFhpZnVENExhaERBNVcyWkpVTk9YcHBjT1lFK2xvUW5rbFdjYzAwekdONHhMU1hMbFBoWFV0bXBra2FuQ1dzUWVMYWoyRUJoU3huRFhpZnVEVkscHBjT1l1FK2xvUW5rb5FERBNVcyWkpVTk9YcHBjT1lFK2xvUW5rbFdjYzAwekdONHhMU1hMbFBoWFV0bXBra2FuQ1dzUWVMYWoyRUJoUhuRFhpZnVEyZE9WNGJtQUhMM2lSZ1JWXVzWldKaUROeThadVONVVNUlJ3N3NFVFJZMwkpVTk9YcHBjT1lF2xvUW5rbFdjYzAwekdONHhMU1hMbFBoWFV0bXBra2FuQ1dzUWVMYWoyRUJS2dBOU9Z4cHBjT1lFK2xvUW5rbFdjYzAwekdONHhMU1hMbFBoWFV0bXBra772Fu1dzUWVMYWoyRUJS2dBOUZ4NExhaERBNVcykpVTk9YcHBjT1lFK2xvUW5rbFdjYzAwekdONHhMU1hMbFBoWFV0bXBra2FuQ1dzUWVMYWoyRUJoUhuRFhpZnVENExhaERBNVcyWkpVTk9YcHBjT1lFK2xvUW5rbFdjYzAwekdONHhMU1hMbFBoWFV0bXBra2FuQ1dzUWVMYWoyRUJU3huRFhpZnVEVkscHBjT1lFK2xvUW5rbFdjYzAwekdONHhMU1hMbFBoWFV0bXBra2FuQ1dUWVMYWoyRUJS2dBOUZ4NExhaERBNVcyWkpVTk9YcHBjT1lFK2xvUW5rbFdjYzAwekdONHhMU1hMbFBoWFV0bXBra2FuQ1dzUWVMYWoyRUJoU3huRFhpZnVEyZE9WNGJtQUhMM2lSZ1J0WXVzWldKaUROeThadTVONVVNUlJ3N3NFVFJZM2w_.pdf”
\n","event":[{"listen":"prerequest","script":{"type":"text/javascript","exec":[""],"id":"507abf68-f4e9-45b1-92ae-354a27731b35"}},{"listen":"test","script":{"type":"text/javascript","exec":[""],"id":"1ba31a4d-26f6-4aef-8348-364da8af3d10"}}],"_postman_id":"42641d8a-4578-4efb-ae9d-d819c8c83958"},{"name":"Staging (RapidLEI customer testing)","item":[{"name":"General - API Health Check","id":"63d21571-7034-41a9-b08b-bbb01a349159","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"GET","header":[],"url":"https://apistaging.rapidlei.com/v1/health","description":"The health endpoint is used to determine the current version of the RapidLEI API service e.g.
\n{\n\"version\": \"3.7.12\"\n}\n\nThe Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. The OAuth2 specification (RFC 6749) requires this content type for token requests. Any other content-type will break OAuth2 compliant clients compatibility.
\n","key":"Content-Type","name":"Content-Type","type":"text","value":"application/x-www-form-urlencoded"},{"description":"The Accept request-header field can be used to specify certain media types which are acceptable for the response. The Accept request HTTP header advertises which content types, expressed as MIME types, the client is able to understand.
\n","key":"Accept","type":"text","value":"application/json"}],"body":{"mode":"urlencoded","urlencoded":[{"key":"grant_type","value":"client_credentials","description":"The grant_type parameter must be set to client_credentials
\n","type":"text"},{"key":"client_id","value":"reseller.email@test.com","description":"The client_id parameter must be set to reseller email address
\n","type":"text"},{"key":"client_secret","value":"xxxxxxAPI_key_from_My_Settingsxxxxxx","description":"The client_secret parameter must be set to API key
\n","type":"text"}]},"url":"https://apistaging.rapidlei.com/v1/auth/token","description":"This call requires an API Key from the 'My Settings' section of your account and the email address of the account. It delivers a Bearer Access Token to authenticate subsequent requests and a time to expiry in seconds. Within the Staging Environment the bearer token lasts for 3000 seconds (Allowing for manual use within a Postman collection), but within production this is limited to 900 seconds.
\n","urlObject":{"protocol":"https","path":["v1","auth","token"],"host":["apistaging","rapidlei","com"],"query":[],"variable":[]}},"response":[{"id":"c7e90022-e0cc-414a-80a6-68e8217c1c31","name":"Successful Response – access_token, token_type, expires_in parameters returned","originalRequest":{"method":"POST","header":[{"key":"Content-Type","name":"Content-Type","value":"application/x-www-form-urlencoded","type":"text"},{"key":"Accept","value":"application/json","type":"text"}],"body":{"mode":"urlencoded","urlencoded":[{"key":"grant_type","value":"client_credentials","description":"The grant_type parameter must be set to client_credentials","type":"text"},{"key":"client_id","value":"reseller.email@test.com","description":"The client_id parameter must be set to reseller email address","type":"text"},{"key":"client_secret","value":"123456789ABCDEF","description":"The client_secret parameter must be set to API key","type":"text"}]},"url":"https://apistaging.rapidlei.com/v1/auth/token"},"status":"OK","code":200,"_postman_previewlanguage":"json","header":[{"key":"Content-Type","value":"application/json","description":"","type":"text"},{"key":"Cache-Control","value":"no-store","description":"","type":"text"},{"key":"Pragma","value":"no-cache","description":"","type":"text"}],"cookie":[],"responseTime":null,"body":"{\n \"access_token\": \"MTQ0NjJkZmQ5OTM2NDE1ZTZjNGZmZjI3\",\n \"token_type\": \"bearer\",\n \"expires_in\": 30000\n}"},{"id":"a47517f9-764c-4420-a6bb-ffd49847bc5b","name":"Unsuccessful Request – Client Authentication Failed","originalRequest":{"method":"POST","header":[{"key":"Content-Type","name":"Content-Type","value":"application/x-www-form-urlencoded","type":"text"},{"key":"Accept","value":"application/json","type":"text"}],"url":"https://apistaging.rapidlei.com/v1/auth/token"},"status":"Unauthorized","code":401,"_postman_previewlanguage":"json","header":[{"key":"Content-Type","value":"application/json","description":"","type":"text"},{"key":"Cache-Control","value":"no-store","description":"","type":"text"},{"key":"Pragma","value":"no-cache","description":"","type":"text"}],"cookie":[],"responseTime":null,"body":"{\r\n \"orderStatus\": \"authorization_error\",\r\n \"message\": \" Client Authentication failed due to either an invalid client_id (email address) or client_secret (API key from My Settings)\",\r\n \"errorUri\": \"https://rapidlei.com/api\"\r\n}"},{"id":"397c5145-0562-42f9-9e45-f4128df4a027","name":"Unsuccessful Request – Missing Request Parameter","originalRequest":{"method":"POST","header":[{"key":"Content-Type","name":"Content-Type","value":"application/x-www-form-urlencoded","type":"text"},{"key":"Accept","value":"application/json","type":"text"}],"body":{"mode":"urlencoded","urlencoded":[{"key":"grant_type","value":"client_credentials","description":"The grant_type parameter must be set to client_credentials","type":"text"},{"key":"client_id","value":"reseller.email@test.com","description":"The client_id parameter must be set to reseller email address","type":"text"}]},"url":"https://apistaging.rapidlei.com/v1/auth/token"},"status":"Bad Request","code":400,"_postman_previewlanguage":"json","header":[{"key":"Content-Type","value":"application/json","description":"","type":"text"},{"key":"Cache-Control","value":"no-store","description":"","type":"text"},{"key":"Pragma","value":"no-cache","description":"","type":"text"}],"cookie":[],"responseTime":null,"body":"{\r\n \"orderStatus\": \"invalid_request\",\r\n \"message\": \"Request is missing the 'client_secret' parameter\",\r\n\t\"errorUri\": \"https://rapidlei.com/api\"\r\n}"},{"id":"2813615a-0cb1-42bf-bd0c-03a51bef9269","name":"Unsuccessful Request – Internal Server Error or Exception","originalRequest":{"method":"POST","header":[{"key":"Content-Type","name":"Content-Type","value":"application/x-www-form-urlencoded","type":"text"},{"key":"Accept","value":"application/json","type":"text"}],"body":{"mode":"urlencoded","urlencoded":[{"key":"grant_type","value":"client_credentials","description":"The grant_type parameter must be set to client_credentials","type":"text"},{"key":"client_id","value":"reseller.email@test.com","description":"The client_id parameter must be set to reseller email address","type":"text"},{"key":"client_secret","value":"123456789ABCDEF","description":"The client_secret parameter must be set to API key","type":"text"}]},"url":"https://apistaging.rapidlei.com/v1/auth/token"},"status":"Internal Server Error","code":500,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\r\n \"orderStatus\": \"server_error\",\r\n \"message\": \"Internal server error - If this problem persists, please contact the support team\",\r\n \"errorUri\": \"https://rapidlei.com/api\"\r\n}"},{"id":"b549d8cf-c713-4267-b9a4-8798d5db4653","name":"Unsuccessful Request – Unsupported or Missing Grant Type","originalRequest":{"method":"POST","header":[{"key":"Content-Type","name":"Content-Type","value":"application/x-www-form-urlencoded","type":"text"},{"key":"Accept","value":"application/json","type":"text"}],"body":{"mode":"urlencoded","urlencoded":[{"key":"grant_type","value":"password","description":"The grant_type parameter must be set to client_credentials","type":"text"},{"key":"client_id","value":"reseller.email@test.com","description":"The client_id parameter must be set to reseller email address","type":"text"},{"key":"client_secret","value":"123456789ABCDEF","description":"The client_secret parameter must be set to API key","type":"text"}]},"url":"https://apistaging.rapidlei.com/v1/auth/token"},"status":"Bad Request","code":400,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\r\n \"orderStatus\": \"unsupported_grant_type\"\r\n}"}],"_postman_id":"16c88a37-ea74-48e9-9c83-8b3274f53574"},{"name":"Accounts - User Information","id":"fb716b8e-52ee-417b-9a02-1e22135adfe4","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"GET","header":[{"key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"key":"Content-Type","type":"text","value":"application/json"}],"url":"https://apistaging.rapidlei.com/v1/accounts/userinfo","description":"The userinfo endpoint is a secured API that returns basic information about the authenticated user.
\n","urlObject":{"protocol":"https","path":["v1","accounts","userinfo"],"host":["apistaging","rapidlei","com"],"query":[],"variable":[]}},"response":[],"_postman_id":"fb716b8e-52ee-417b-9a02-1e22135adfe4"},{"name":"Accounts - Create User","id":"bbf1ae9b-cd78-4b73-ade5-91f7b0c1fd00","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.
\n","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity.
\n","key":"Content-Type","type":"text","value":"application/json"}],"body":{"mode":"raw","raw":"{\r\n \"firstName\": \"Peter\",\r\n \"lastName\": \"Anderson\",\r\n \"email\": \"useremail@server.com\",\r\n \"leiNumber\": \"984500B12AE2CF0PF040\"\r\n}"},"url":"https://apistaging.rapidlei.com/v1/accounts/users","description":"This endpoint adds a new user to the RapidLEI platform. A bearer access token from 'Authentication - Request Access Token' is required to submit the request. The new user's account will be linked to the Partners' LEI provided in the call. All users added to the platform will need to complete the registration process and agree to terms before being added. An email based challenge/response to the email address provided in the call verifies permission and email accuracy. If the challenge is not completed within 6 days, the entry will be deleted from the system (GDPR Privacy by Design). A web based system is available too. See 'Referral Link' details on https://rapidlei.com/partners/partner-resources/
\nPlease note that the Staging System does not have any ability to send emails other than to a default catchall of testing(a)rapidlei.com, so please discuss with the support team support(a)rapidlei.com to be able to test this function.
\nFinally, please note that you may be enabled to use this API call, but not the 'Full' LEI API. Please discuss with the support team support(a)rapidlei.com
\n","urlObject":{"protocol":"https","path":["v1","accounts","users"],"host":["apistaging","rapidlei","com"],"query":[],"variable":[]}},"response":[{"id":"675f253e-051a-494b-814f-fd61a3eed7f7","name":"Successful Response – User Created","originalRequest":{"method":"POST","header":[{"key":"Authorization","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx","description":"he Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","type":"text"},{"key":"Content-Type","value":"application/json","description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","type":"text"}],"body":{"mode":"raw","raw":"{\r\n \"firstName\": \"Peter\",\r\n \"lastName\": \"Anderson\",\r\n \"email\": \"useremail@server.com\",\r\n \"leiNumber\": \"984500B12AE2CF0PF040\",\r\n \"organizationName\": \"Legal Entity Name Limited\"\r\n}","options":{"raw":{"language":"json"}}},"url":"https://apistaging.rapidlei.com/v1/accounts/users"},"status":"OK","code":200,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"message\": \"User created successfully.\"\n}"},{"id":"f67b4785-4aa3-4bcf-a891-e29007c4f7f4","name":"Unsuccessful Response – Referrer LEI is not found or not managed by RapidLEI","originalRequest":{"method":"POST","header":[{"key":"Authorization","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx","description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","type":"text"},{"key":"Content-Type","value":"application/json","description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","type":"text"}],"body":{"mode":"raw","raw":"{\r\n \"firstName\": \"Peter\",\r\n \"lastName\": \"Anderson\",\r\n \"email\": \"useremail@server.com\",\r\n \"leiNumber\": \"123400B12AE2CF0PF040\",\r\n \"organizationName\": \"Legal Entity Name Limited\"\r\n}","options":{"raw":{"language":"json"}}},"url":"https://apistaging.rapidlei.com/v1/accounts/users"},"status":"Internal Server Error","code":500,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderStatus\": \"server_error\",\n \"message\": \"The 'leiNumber' parameter needs to be an LEI managed by RapidLEI and linked with your account. Please contact our support team to discuss options.\",\n \"errorUri\": \"https://rapidlei.com/api\"\n}"},{"id":"5715f3f6-754d-45b1-aabf-7edc3e088ad4","name":"Unsuccessful Response – Parameter Missing","originalRequest":{"method":"POST","header":[{"key":"Authorization","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx","description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","type":"text"},{"key":"Content-Type","value":"application/json","description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","type":"text"}],"body":{"mode":"raw","raw":"{\r\n \"lastName\": \"Anderson\",\r\n \"email\": \"useremail@server.com\",\r\n \"leiNumber\": \"984500B12AE2CF0PF040\",\r\n \"organizationName\": \"Legal Entity Name Limited\"\r\n}","options":{"raw":{"language":"json"}}},"url":"https://apistaging.rapidlei.com/v1/accounts/users"},"status":"Bad Request","code":400,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderStatus\": \"invalid_request\",\n \"message\": \"Request is missing the 'firstName' parameter\",\n \"errorUri\": \"https://rapidlei.com/api\"\n}"},{"id":"18101b2f-b51b-43c3-b6aa-4c6ce0e1f8d3","name":"Unsuccessful Response – Invalid Email Address","originalRequest":{"method":"POST","header":[{"key":"Authorization","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx","description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","type":"text"},{"key":"Content-Type","value":"application/json","description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","type":"text"}],"body":{"mode":"raw","raw":"{\r\n \"firstName\": \"Peter\",\r\n \"lastName\": \"Anderson\",\r\n \"email\": \"useremailserver.com\",\r\n \"leiNumber\": \"984500B12AE2CF0PF040\",\r\n \"organizationName\": \"Legal Entity Name Limited\"\r\n}","options":{"raw":{"language":"json"}}},"url":"https://apistaging.rapidlei.com/v1/accounts/users"},"status":"Bad Request","code":400,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{ \r\n \"orderStatus\": \"invalid_request\", \r\n \"message\": \"Please provide a valid email address format user@domain.com or first.last@domain.co.uk etc\", \r\n \"errorUri\": \"https://rapidlei.com/api\" \r\n}"},{"id":"b49b67a8-75c6-400f-a0c8-d0d73ea8d7be","name":"Unsuccessful Response – Invalid LEI Format","originalRequest":{"method":"POST","header":[{"key":"Authorization","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx","description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","type":"text"},{"key":"Content-Type","value":"application/json","description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","type":"text"}],"body":{"mode":"raw","raw":"{\r\n \"firstName\": \"Peter\",\r\n \"lastName\": \"Anderson\",\r\n \"email\": \"useremail@server.com\",\r\n \"leiNumber\": \"984500B12AE2CF0PF0\",\r\n \"organizationName\": \"Legal Entity Name Limited\"\r\n}","options":{"raw":{"language":"json"}}},"url":"https://apistaging.rapidlei.com/v1/accounts/users"},"status":"Bad Request","code":400,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderStatus\": \"invalid_request\",\n \"message\": \"Please ensure the 'leiNumber' is a valid ISO 17442 format LEI (20 characters).\",\n \"errorUri\": \"https://rapidlei.com/api\"\n}"},{"id":"a2b7b8d3-cb17-44d0-8047-24b737f23785","name":"Unsuccessful Response – Request to add user failed as the user already exists","originalRequest":{"method":"POST","header":[{"key":"Authorization","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx","description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","type":"text"},{"key":"Content-Type","value":"application/json","description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","type":"text"}],"body":{"mode":"raw","raw":"{\r\n \"firstName\": \"Peter\",\r\n \"lastName\": \"Anderson\",\r\n \"email\": \"useremail@server.com\",\r\n \"lei\": \"984500B12AE2CF0PF040\",\r\n \"organizationName\": \"Legal Entity Name Limited\"\r\n}","options":{"raw":{"language":"json"}}},"url":"https://apistaging.rapidlei.com/v1/accounts/users"},"status":"Internal Server Error","code":500,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderStatus\": \"server_error\",\n \"message\": \"We already have a user account with the email address supplied. If in doubt please contact our support team.\",\n \"errorUri\": \"https://rapidlei.com/api\"\n}"},{"id":"4f116e02-691a-45dc-b5d3-522a9154e912","name":"Unsuccessful Response – Referrer feature is not enabled","originalRequest":{"method":"POST","header":[{"key":"Authorization","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx","description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","type":"text"},{"key":"Content-Type","value":"application/json","description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","type":"text"}],"body":{"mode":"raw","raw":"{\r\n \"firstName\": \"Peter\",\r\n \"lastName\": \"Anderson\",\r\n \"email\": \"useremail@server.com\",\r\n \"leiNumber\": \"984500B12AE2CF0PF040\",\r\n \"organizationName\": \"Legal Entity Name Limited\"\r\n}","options":{"raw":{"language":"json"}}},"url":"https://apistaging.rapidlei.com/v1/accounts/users"},"status":"Internal Server Error","code":500,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderStatus\": \"server_error\",\n \"message\": \"Sorry, you are unable to add users. The Referrer feature has not been enabled for your account. If in doubt, please talk to our support team.\",\n \"errorUri\": \"https://rapidlei.com/api\"\n}"},{"id":"561eb216-d724-48e4-b8d5-4905a1dfdf0c","name":"Unsuccessful Response – Parameter Length Error","originalRequest":{"method":"POST","header":[{"key":"Authorization","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx","description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","type":"text"},{"key":"Content-Type","value":"application/json","description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","type":"text"}],"body":{"mode":"raw","raw":"{\r\n \"firstName\": \"Peter middle name example is much bigger than we allow\",\r\n \"lastName\": \"Anderson\",\r\n \"email\": \"useremail@server.com\",\r\n \"leiNumber\": \"984500B12AE2CF0PF040\",\r\n \"organizationName\": \"Legal Entity Name Limited\"\r\n}","options":{"raw":{"language":"json"}}},"url":"https://apistaging.rapidlei.com/v1/accounts/users"},"status":"Bad Request","code":400,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderStatus\": \"invalid_request\",\n \"message\": \"Parameter 'firstName' should not be greater than 50 characters\",\n \"errorUri\": \"https://rapidlei.com/api\"\n}"},{"id":"2a74c923-861c-49f4-87bb-6a5b50d36b13","name":"Unsuccessful Response – Missing organizaionName","originalRequest":{"method":"POST","header":[{"key":"Authorization","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx","description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","type":"text"},{"key":"Content-Type","value":"application/json","description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","type":"text"}],"body":{"mode":"raw","raw":"{\r\n \"firstName\": \"Peter\",\r\n \"lastName\": \"Anderson\",\r\n \"email\": \"useremail@server.com\",\r\n \"leiNumber\": \"984500B12AE2CF0PF040\"\r\n}","options":{"raw":{"language":"json"}}},"url":"https://apistaging.rapidlei.com/v1/accounts/users"},"status":"Bad Request","code":400,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderStatus\": \"invalid_request\",\n \"message\": \"Request is missing the 'organizaionName' parameter\",\n \"errorUri\": \"https://rapidlei.com/api\"\n}"}],"_postman_id":"bbf1ae9b-cd78-4b73-ade5-91f7b0c1fd00"},{"name":"LEI – Pre-Submission Entity Search","id":"5fc118e2-73fd-49ec-9dc5-63f83afc5419","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.
\n","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity.
\n","key":"Content-Type","name":"Content-Type","type":"text","value":"application/json"}],"body":{"mode":"raw","raw":"{\r\n \"keyword\": \"Ubisecure Holdings\",\r\n \"legalJurisdiction\": \"GB\",\r\n \"entityType\": \"GENERAL\"\r\n}","options":{"raw":{"language":"json"}}},"url":"https://apistaging.rapidlei.com/v1/leis/searchByKeyword","description":"The Pre-Submission Entity Search ensures data accuracy for New LEI or Import LEI requests by performing an initial search of the jurisdiction. Legal Name spelling, form and capitalization as well as Registration Authority Entity ID (Business Registry Number) accuracy are improved using this API endpoint. The API Endpoint returns one or more potential legal entities along with a 'searchId' and 'companyId' - Please see LEI – Create New LEI and LEI – Import Existing LEI for details.
\nIt is highly recommended to search by the Business Registry Number first as this is the most accurate method. The name of the Legal Entity may be too generic and may return too many results to display all, resulting in the entity not being found.
\nThe keyword helps identify the Legal Entity. It can be either:
\nName of the Legal Entity e.g. ABC Limited
\nCompany Number for the Legal Entity e.g. 68678678
\nThe LEI number to be imported/transferred. e.g. 89450051ZRDOL9KEWH63
\nlegalJurisdiction
\nA supported legal jurisdiction is required. e.g. DK or US-CA for California in the United States
\nPlease note that the following entityType's are NOT supported within the pre-submission search:-
\nThe Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.
\n","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity.
\n","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://apistaging.rapidlei.com/v1/jurisdictions","description":"This API call is used to query supported jurisdictions and confidence levels. Confidence level 10 is fully automated including Authorised Representative verification resulting in rapid, efficient LEI issuance. Confidence level 0 is a manually processed jurisdiction requiring manual verification of data on the business registry. Confidence levels 1-9 indicate the expected confidence level in gathering data from the registry. 9 indicates all LE-RD Level 1 data is usually available. 8 indicates most LE-RD Level 1 data is usually available. For additional details on how best to use this function please contact the RapidLEI support team.
\n","urlObject":{"protocol":"https","path":["v1","jurisdictions"],"host":["apistaging","rapidlei","com"],"query":[],"variable":[]}},"response":[{"id":"6567532b-3f85-4c4b-8882-078639fc3b9e","name":"Successful Response – List of Jurisdictions returned","originalRequest":{"method":"GET","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://apistaging.rapidlei.com/v1/jurisdictions"},"status":"OK","code":200,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"countries\": [\n {\n \"jurisdiction\": \"DK\",\n \"confidenceLevel\": \"10\"\n },\n {\n \"jurisdiction\": \"HK\",\n \"confidenceLevel\": \"0\"\n },\n {\n \"jurisdiction\": \"NL\",\n \"confidenceLevel\": \"7\"\n }\n ],\n \"states\": [\n\t {\n\t \"jurisdiction\": \"US-KS\",\n\t \"confidenceLevel\": \"10\"\n\t },\n\t {\n\t \"jurisdiction\": \"US-NJ\",\n\t \"confidenceLevel\": \"6\"\n\t },\n\t {\n\t \"jurisdiction\": \"US-DC\",\n\t \"confidenceLevel\": \"0\"\n\t }\n ]\n}"},{"id":"80e7ed05-b100-4e24-a3e1-99b5a8004d1d","name":"Unsuccessful Response - User not allowed to use the Full API, only the ‘Create User’ endpoint","originalRequest":{"method":"GET","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://apistaging.rapidlei.com/v1/jurisdictions"},"status":"Unauthorized","code":401,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderStatus\": \"authorization_error\",\n \"message\": \"You do not have the ability to use the Full RapidLEI API from this account – you are configured only to use the ‘Create User’ endpoint, please contact our support team on support@rapidlei.com\",\n \"errorUri\": \"https://rapidlei.com/api\"\n}"},{"id":"40afd0b3-0f3a-4692-acb2-6d8378cae5fc","name":"Unsuccessful Response - Unknown Error or Exception during processing request","originalRequest":{"method":"GET","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://apistaging.rapidlei.com/v1/jurisdictions"},"status":"Internal Server Error","code":500,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderStatus\": \"server_error\",\n \"message\": \"We've been unable to process your request - please contact our support team.\",\n \"errorUri\": \"https://rapidlei.com/api\"\n}"}],"_postman_id":"45afc67b-5209-40b7-919a-aea8a7f70f32"},{"name":"LEI - Create New LEI","id":"c8768737-55a1-4ba9-bec6-1c87d770cef0","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.
\n","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity.
\n","key":"Content-Type","name":"Content-Type","type":"text","value":"application/json"}],"body":{"mode":"raw","raw":"{\n \"companyName\": \"ABC Limited\",\n \"companyNumber\": \"68678678\",\n \"searchId\": \"9cf0521c2dfc4502bfa3f7bb49daca77\",\n \"companyId\": \"8ba68d90a7324ba2bbbbe87bc227c461\",\n \"legalJurisdiction\": \"DK\",\n \"firstName\": \"Peter\",\n \"lastName\": \"Anderson\",\n \"isLevel2DataAvailable\": false,\n \"reportingExceptionReason\": \"NATURAL_PERSONS\",\n \"multiYearSupport\": 3,\n \"entityType\": \"GENERAL\",\n \"userComments\": \"optional comments\",\n \"notificationUrl\": \"https://www.someotherserver.com/notify/me/when/lei/is/ready\",\n \"notificationToken\": \"Sq31YkqGWKXGEpeJGZwM\",\n \"loaFile\": {\n \"fileName\": \"My Letter of Authorization.docx\",\n \"fileUrl\": \"http://www.example.com/LoA.docx?token=GFVHGSahG6HGjsggdgxxSecurity-Token-examplexxGFDsdd\"\n },\n \"corroboratingFiles\": [\n {\n \"fileName\": \"Corroborating Data 1.docx\",\n \"fileUrl\": \"http://www.example.com/file.docx\"\n },\n {\n \"fileName\": \" Corroborating Data 2.docx\",\n \"fileData\": \"data:application/octet–stream;base64, ldfhaklsjdfhkasjfjsdfgakjsfgakjsdagsdf...\"\n }\n ]\n}"},"url":"https://apistaging.rapidlei.com/v1/leis/orders/create","description":"This API endpoint initiates the workflow process to request a new LEI (i.e. An LEI will be created, so the call assumes that the Legal Entity does not already have an LEI, but it also tests that assumption and will provide an error if one is found - see the examples for more information). The bearer access Token from 'Authentication - Request Access Token' is required to submit the request along with the following mandatory / optional parameters.
\nPlease note GDPR (General Data Protection Regulations) when transferring personal data. Ensure permission of the Legal Entity.
\ncompanyName
Name of the Legal Entity noting that accuracy here helps the overall process flow and accuracy of any potential duplicate test. e.g. ABC Limited
companyNumber
Company Number, (Registration Authority Entity ID) for the Legal Entity noting that accuracy here helps the overall process flow and accuracy of any potential duplicate test. e.g. 068678678 - Tip - don't forget to ensure any leading '0's are maintained - this is common for UK based numbers. For Funds which sometimes do not have a Registration Authority Entity ID, you may leave this field empty ensuring entityType is set to FUND. There may be a legitimate edge case such as a Legal Entity in Germany, or South Carolina which does not have any number. In these rare cases please use entityType OTHER
legalJurisdiction
A supported legal jurisdiction is required. e.g. DK or US-CA for California in the United States
firstName
The First Name(s) of the Authorised Representative with the responsibility/authority to request and approve the creation of an LEI e.g. Peter
lastName
The Last Name of the Authorised Representative e.g. Anderson
isLevel2DataAvailable
A Boolean value - If the Legal Entity consolidates accounts with parental entities, then Level 2 data will be required. This data is not to be provided by API calls. Due to the complex nature of the data possibilities, the GUI interface of the RapidLEI Identity Platform must be used i.e. true if level 2 data is available and false if reporting exceptions are to be used.
multiYearSupport
An integer from 1 to 5. Please see https://rapidlei.com/lei-pricing/ for details. Please default to 1 as the standard option.
reportingExceptionReason
If isLevel2DataAvailable is set to false, then it indicates there is no level 2 information, so please highlight the appropriate reporting exception reason which will be used for BOTH Direct and Ultimate Parent reporting. If any other combination of reporting exceptions is required, please set isLevel2DataAvailable to true and use the GUI
NATURAL_PERSONS
\nNON_CONSOLIDATING
\nNO_KNOWN_PERSON
\nPrior to the release of LE-RR Version 2.1, the following reasons were specifically used for Level 2 scenarios where parental accounting was present, but LEI details were absent. The removal of PNI data by the ROC (Regulatory Oversight Committee) has deprecated these exception reasons. Please see this announcement for details (https://www.leiroc.org/publications/gls/roc_20220107.pdf)
\nDeprecated exception reasons:-
\nCONSENT_NOT_OBTAINED
\nLEGAL_OBSTACLES
\nBINDING_LEGAL_COMMITMENTS
\nDETRIMENT_NOT_EXCLUDED
\nDISCLOSURE_DETRIMENTAL
\nHave been replaced by a single reporting exception configured within the GUI along with other level 2 parental reporting and Fund reporting options:-
\nsearchId & companyId
When the LEI – Pre-Submission Entity Search function is used prior to a New LEI being created, submission of the 'searchId' and 'companyId' togther with the EXACT Name of the companyName, legalJurisdiction and companyNumber will accelerate the speed at which the LEI is issued.
entityType
If entityType is not included, we'll assume the request is for a legal entity. A positive indication of the entityType will increase the efficiency of the RapidLEI vetting team and any associated workflows.
GENERAL
\nSOLE_PROPRIETOR
\nFUND
\nWILL_PENSION
\nTRUST
\nOTHER
\nNotes:- If Submitting a FUND it is advisable to include the fund deed as 'Evidence of Authority' in the corroboratingFiles as this will avoid the need to ask for this document.
\nnotificationUrl
To avoid unnecessary polling, webhooks can be used to pass orderStatus information in real time. A webhook is a user-defined HTTP (ideally HTTPS) endpoints which can accept POST requests for real time synchronous LEI processing. An optional security token may be used to avoid replay attacks, however the notificationUrl may also contain additional URL parameters. Webhook ApS in Denmark, ran by Simon Fredsted, offers a very simple listening service for testing webhooks. Please see https://webhook.site/ for details and usage guidelines. The two parameters returned in the RequestBody are - orderTrackingCode and orderStatus, with the optional security token being returned as notificationTokene.g. https://www.someotherserver.com/notify/me/when/lei/is/ready
or https://www.someotherserver.com/notify/me/when/lei/is/ready?type=exampletype&token=URL_based_token_examplePLEASE NOTE - Redirects are not guaranteed to be supported in all cases therefore please ensure the correct URL and any final / characters in the URL are sent.
notificationToken
An optional unique token to avoid the possibility of a third party accidentally making a call to a static notification URL and therefore maliciously affecting the workflow.
e.g. Sq31YkqGWKXGEpeJGZwM\"
userComments
An optional comment or instruction to aid efficient processing of the LEI by the RapidLEI vetting team – to be used primarily for simple comments < 1000 characters to avoid the need to send additional corroborating documents.
corroboratingFiles Up to 5 additional files which may aid vetting or validation of the Application. Please note the upload limit of 20MB each.
\nnextRenewalDate
nextRenewalDate is an advanced customization option which requires multi-year support and is applicable to enterprises who require alignment of LEI issuance/renewal around specific dates. Please discuss in detail before implementing this function. nextRenewalDate is a date in the future which indicates the 'nextRenewalDate' of the LEI. If omitted, the date will be set to one calendar year from initial issuance of the LEI.
is3rdPartyRequest
If is3rdPartyRequest is set to true an LoA MUST be uploaded which highlights the agreement between the 3rd Party and the Legal Entity. For more details please discuss with our legal team legal(a)rapidlei.com. Please discuss in detail before implementing this function
The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.
\n","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity.
\n","key":"Content-Type","type":"text","value":"application/json"}],"body":{"mode":"raw","raw":"{\n \"companyName\": \"ABC Limited\",\n \"companyNumber\": \"68678678\",\n \"leiNumber\": \"213800855GFRCT277149\",\n \"legalJurisdiction\": \"DK\",\n \"firstName\": \"Peter\",\n \"lastName\": \"Anderson\",\n \"email\": \"peter.anderson@testmail.com\",\n \"phone\": \"003489348573945\",\n \"isLevel2DataAvailable\": false,\n \"reportingExceptionReason\": \"NATURAL_PERSONS\",\n \"multiYearSupport\": 3,\n \"userComments\": \"optional comments\",\n \"notificationUrl\": \"https://www.someotherserver.com/notify/me/when/lei/is/ready\",\n \"notificationToken\": \"Sq31YkqGWKXGEpeJGZwM\",\n \"mergedOrRetiredLeiComments\": \"Optional comments to mention the reasons to import MERGED or RETIRED LEI\",\n \"loaFile\": {\n \"fileName\": \"My Letter of Authorization.docx\",\n \"fileUrl\": \"http://www.example.com/LoA.docx?token=GFVHGSahG6HGjsggdgxxSecurity-Token-examplexxGFDsdd\"\n },\n \"corroboratingFiles\": [\n {\n \"fileName\": \"Corroborating Data 1.docx\",\n \"fileUrl\": \"http://www.example.com/file.docx\"\n },\n {\n \"fileName\": \" Corroborating Data 2.docx\",\n \"fileData\": \"data:application/octet–stream;base64, ldfhaklsjdfhkasjfjsdfgakjsfgakjsdagsdf...\"\n }\n ]\n}"},"url":"https://apistaging.rapidlei.com/v1/leis/orders/import","description":"This API endpoint initiates the workflow process to transfer an existing LEI (i.e. An LEI must already exist and have a GLEIF Status of ISSUED, LAPSED or rarely RETIRED). The bearer access Token from 'Authentication - Request Access Token' is required to submit the request along with the following mandatory / optional parameters.
\nPlease note GDPR (General Data Protection Regulations) when transferring personal data. Ensure permission of the Legal Entity.
\ncompanyName
Name of the Legal Entity noting that accuracy here helps the overall process flow and accuracy of any potential duplicate test. e.g. ABC Limited
companyNumber
Company Number, (Registration Authority Entity ID) for the Legal Entity noting that accuracy here helps the overall process flow and accuracy of any potential duplicate test. e.g. 068678678 - Tip - don't forget to ensure any leading '0's are maintained - this is common for UK based numbers. For Funds which sometimes do not have a Registration Authority Entity ID, you may leave this field empty ensuring entityType is set to FUND. There may be a legitimate edge case such as a Legal Entity in Germany, or South Carolina which does not have any number. In these rare cases please use entityType OTHER
legalJurisdiction
A supported legal jurisdiction is required. e.g. DK or US-CA for California in the United States
leiNumber
The LEI number to be imported/transferred.
e.g. 89450051ZRDOL9KEWH63
firstName
The First Name(s) of the Authorised Representative with the responsibility/authority to request and approve the creation of an LEI e.g. Peter
lastName
The Last Name of the Authorised Representative e.g. Anderson
email
The email of the contact person who is authorized to request the transfer of the LEI e.g. peter.anderson@testmail.com (Please note that this is a requirement of the GLEIF LEI Transfer Protocol and must be transferred as part of the initial call. This differs from the creation of an LEI where this information is not usually taken – please ensure permission of the Legal Entity to allow the transfer of this personal data)
phone
The phone number of the contact person who is authorized to request the transfer of the LEI e.g. 003489348573945 (Please note that this is a requirement of the GLEIF LEI Transfer Protocol and must be transferred as part of the initial call. This differs from the creation of an LEI where this information is not usually taken – please ensure permission of the Legal Entity to allow the transfer of this personal data)
isLevel2DataAvailable
A Boolean value - If the Legal Entity consolidates accounts with parental entities, then Level 2 data will be required. This data is not to be provided by API calls. Due to the complex nature of the data possibilities, the GUI interface of the RapidLEI Identity Platform must be used i.e. true if level 2 data is available and false if reporting exceptions are to be used.
multiYearSupport
An integer from 1 to 5. Please see https://rapidlei.com/lei-pricing/ for details. Please default to 1 as the standard option.
reportingExceptionReason
If isLevel2DataAvailable is set to false, then it indicates there is no level 2 information, so please highlight the appropriate reporting exception reason which will be used for BOTH Direct and Ultimate Parent reporting. If any other combination of reporting exceptions is required, please set isLevel2DataAvailable to true and use the GUI
NATURAL_PERSONS
\nNON_CONSOLIDATING
\nNO_KNOWN_PERSON
\nPrior to the release of LE-RR Version 2.1, the following reasons were specifically used for Level 2 scenarios where parental accounting was present, but LEI details were absent. The removal of PNI data by the ROC (Regulatory Oversight Committee) has deprecated these exception reasons. Please see this announcement for details (https://www.leiroc.org/publications/gls/roc_20220107.pdf)
\nDeprecated exception reasons:-
\nCONSENT_NOT_OBTAINED
\nLEGAL_OBSTACLES
\nBINDING_LEGAL_COMMITMENTS
\nDETRIMENT_NOT_EXCLUDED
\nDISCLOSURE_DETRIMENTAL
\nHave been replaced by a single reporting exception configured within the GUI along with other level 2 parental reporting and Fund reporting options:-
\nentityType
If entityType is not included, we'll assume the request is for a legal entity. A positive indication of the entityType will increase the efficiency of the RapidLEI vetting team and any associated workflows.
GENERAL
\nSOLE_PROPRIETOR
\nFUND
\nWILL_PENSION
\nTRUST
\nOTHER
\nNotes:- If Submitting a FUND it is advisable to include the fund deed as 'Evidence of Authority' in the corroboratingFiles as this will avoid the need to ask for this document.
\nnotificationUrl
To avoid unnecessary polling, webhooks can be used to pass orderStatus information in real time. A webhook is a user-defined HTTP (ideally HTTPS) endpoints which can accept POST requests for real time synchronous LEI processing. An optional security token may be used to avoid replay attacks, however the notificationUrl may also contain additional URL parameters. Webhook ApS in Denmark, ran by Simon Fredsted, offers a very simple listening service for testing webhooks. Please see https://webhook.site/ for details and usage guidelines. The two parameters returned in the RequestBody are - orderTrackingCode and orderStatus, with the optional security token being returned as notificationTokene.g. https://www.someotherserver.com/notify/me/when/lei/is/ready
or https://www.someotherserver.com/notify/me/when/lei/is/ready?type=exampletype&token=URL_based_token_examplePLEASE NOTE - Redirects are not guaranteed to be supported in all cases therefore please ensure the correct URL and any final / characters in the URL are sent.
notificationToken
An optional unique token to avoid the possibility of a third party accidentally making a call to a static notification URL and therefore maliciously affecting the workflow.
e.g. Sq31YkqGWKXGEpeJGZwM\"
userComments
An optional comment or instruction to aid efficient processing of the LEI by the RapidLEI vetting team – to be used primarily for simple comments < 1000 characters to avoid the need to send additional corroborating documents.
corroboratingFiles Up to 5 additional files which may aid vetting or validation of the Application. Please note the upload limit of 20MB each.
\nnextRenewalDate
nextRenewalDate is an advanced customization option which requires multi-year support and is applicable to enterprises who require alignment of LEI issuance/renewal around specific dates. Please discuss in detail before implementing this function. nextRenewalDate is a date in the future which indicates the 'nextRenewalDate' of the LEI. If omitted, the date will be set to one calendar year from initial issuance of the LEI.
is3rdPartyRequest
If is3rdPartyRequest is set to true an LoA MUST be uploaded which highlights the agreement between the 3rd Party and the Legal Entity. For more details please discuss with our legal team legal(a)rapidlei.com. Please discuss in detail before implementing this function
The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.
\n","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity.
\n","key":"Content-Type","name":"Content-Type","type":"text","value":"application/json"}],"body":{"mode":"raw","raw":"{\n \"orderTrackingCode\": \"YEaadmjQbt00uY0mepcg\",\n \"loaFiles\": [\n {\n \"fileName\": \"LoA1. pdf\",\n \"fileData\": \"data:text/plain;base64,dGVzdA==\"\n },\n {\n \"fileName\": \"LoA2.pdf\",\n \"fileUrl\": \"https://www.lean.org/downloads/sampleboardreport.pdf\"\n }\n ], \n \"eoaFiles\": [\n {\n \"fileName\": \"EoaFile1.docx\",\n \"fileData\": \"data:text/plain;base64,dGVzdA==\"\n },\n {\n \"fileName\": \"EoaFile2.pdf\",\n \"fileUrl\": \"https://www.lean.org/downloads/sampleboardreport.pdf\"\n }\n ],\n \"corroboratingFiles\": [\n {\n \"fileName\": \"CorroboratingFile1.docx\",\n \"fileData\": \"data:text/plain;base64,dGVzdA==\"\n },\n {\n \"fileName\": \"CorroboratingFile2.pdf\",\n \"fileUrl\": \"https://www.lean.org/downloads/sampleboardreport.pdf\"\n }\n ]\n}"},"url":"https://apistaging.rapidlei.com/v1/leis/uploadFiles","description":"This API endpoint mimics the GUI facility to upload files at any time, for any LEI order with an associated ‘orderTrackingCode’. Files can be of type LoA (Letter of Authorization), EoA (Evidence of Authority) or other Corroborating Data. Orders submitted via GUI (Graphical User Interface) or via Bulk XLS methods, do not have unique API ‘orderTrackingCode’ and therefore files must be associated with these orders using the GUI interface only. The bearer access Token from 'Authentication - Request Access Token' is required to submit the request along with the following mandatory / optional parameters.
\n– orderTrackingCode
\nA unique token returned when any New, Import or Renew order is created. e.g. 987a9sd8f7a9sd8f7
\nloaFiles
A Letter of Authorization (LoA) is used to provide linkage between the Applicant applying for the LEI & a Valid Authorised Representative found on a Registry for the Legal Entity. The Applicant applying for the LEI will be the Authorised Representative name submitted as firstName lastName parameters. The Letter of Authorization (LoA) will be a document from one of the Valid Authorised Representatives, this document will state that the valid signer is empowering the Applicant of the LEI (Authorised Representative Name already given) to manage the LEI on their behalf. Please note that if a valid Authorised Authorised Representative wishes to manage the LEI themselves directly then the Authorised Representative Name provided in the order creation can be amended in the GUI.
eoaFiles
Evidence of Authority (EoA) is used to provide additional clarification/evidence of the empowered Authorised Representative name submitted as firstName lastName parameters. A typical common example would be Articles of Association for an LLC in Delaware in the United States which does not maintain records of empowered individuals within their registry. For more details, please discuss with our legal team legal(a)rapidlei.com. Multiple EoA's may be submitted using either the fileData method or fileUrl method. Up to 10 additional files may be uploaded.
corroboratingFiles
Up to 10 additional files which may aid vetting or validation of the Application. Please note the upload limit of 20MB each.
The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.
\n","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity.
\n","key":"Content-Type","name":"Content-Type","type":"text","value":"application/json"}],"body":{"mode":"raw","raw":"{\n \"orderTrackingCode\": \"987a9sd8f7a9sd8f7\",\n \"userComments\": \"Page 10 of the annual report details the level 2 parental structure your vetting team needs\"\n}"},"url":"https://apistaging.rapidlei.com/v1/leis/uploadComments","description":"This API endpoint mimics the GUI facility to upload comments at any time, for any LEI order with an associated ‘orderTrackingCode’. Comments help provide our vetting team with essential details to help process LEI applications more efficiently
\n– orderTrackingCode
\nA unique token returned when any New, Import or Renew order is created. e.g. 987a9sd8f7a9sd8f7
\n– userComments
\nA comment or instruction to aid efficient processing of the LEI by the RapidLEI vetting team – to be used primarily for simple comments < 1000 characters to avoid the need to send additional corroborating documents.
\n","urlObject":{"protocol":"https","path":["v1","leis","uploadComments"],"host":["apistaging","rapidlei","com"],"query":[],"variable":[]}},"response":[{"id":"d3e5d2a7-3a44-4df7-a83f-b1d57c2976a7","name":"Successful Response – Comments Submitted Successfully","originalRequest":{"method":"POST","header":[{"key":"Authorization","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx","description":"A Bearer Token must be set to a valid access token in the Authorization header","type":"text"},{"key":"Content-Type","name":"Content-Type","value":"application/json","description":"The Accept header is used by HTTP clients to tell the server what content types they'll accept.","type":"text"}],"body":{"mode":"raw","raw":"{\r\n \"orderTrackingCode\": \"987a9sd8f7a9sd8f7\",\r\n \"userComments\": \"Page 10 of the annual report details the level 2 parental structure your vetting team needs\"\r\n}","options":{"raw":{"language":"json"}}},"url":"https://apistaging.rapidlei.com/v1/leis/uploadComments"},"status":"OK","code":200,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderTrackingCode\": \"987a9sd8f7a9sd8f7\",\n \"message\": \"userComments successfully submitted\"\n}"},{"id":"82c94089-cffe-4c6e-8281-39638b478861","name":"Unsuccessful Response – All Parameters or entire JSON body missing Copy","originalRequest":{"method":"POST","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"key":"Content-Type","name":"Content-Type","value":"application/json","description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","type":"text"}],"body":{"mode":"raw","raw":"{}","options":{"raw":{"language":"json"}}},"url":"https://apistaging.rapidlei.com/v1/leis/uploadComments"},"status":"Bad Request","code":400,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\r\n \"orderStatus\": \"invalid_request\",\r\n \"message\": \"The request is missing mandatory parameters. Please check our API documentation available at https://rapidlei.com/developers\",\r\n \"errorUri\": \"https://rapidlei.com/api\"\r\n}"},{"id":"4f7d73ba-054d-480f-893c-76219f7a4943","name":"Unsuccessful Response – 'orderTrackingCode' Parameter Missing","originalRequest":{"method":"POST","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"key":"Content-Type","name":"Content-Type","value":"application/json","description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","type":"text"}],"body":{"mode":"raw","raw":"{\r\n \"userComments\": \"Page 10 of the annual report details the level 2 parental structure your vetting team needs\"\r\n}","options":{"raw":{"language":"json"}}},"url":"https://apistaging.rapidlei.com/v1/leis/uploadComments"},"status":"Bad Request","code":400,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\r\n \"orderStatus\": \"invalid_request\",\r\n \"message\": \"Request is missing the 'orderTrackingCode' parameter\",\r\n \"errorUri\": \"https://rapidlei.com/api\"\r\n}"},{"id":"8585acb6-9d56-4fcc-81f2-2fa5da5fc3e6","name":"Unsuccessful Response – 'userComments' Parameter Missing Copy","originalRequest":{"method":"POST","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"key":"Content-Type","name":"Content-Type","value":"application/json","description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","type":"text"}],"body":{"mode":"raw","raw":"{\r\n \"orderTrackingCode\": \"987a9sd8f7a9sd8f7\"\r\n}","options":{"raw":{"language":"json"}}},"url":"https://apistaging.rapidlei.com/v1/leis/uploadComments"},"status":"Bad Request","code":400,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\r\n \"orderStatus\": \"invalid_request\",\r\n \"message\": \"Request is missing the 'userComments' parameter\",\r\n \"errorUri\": \"https://rapidlei.com/api\"\r\n}"},{"id":"ee3ee3eb-6b55-4fc7-8aa9-0657ea7bae0c","name":"Unsuccessful Response – Maximum character limit exceeded","originalRequest":{"method":"POST","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"key":"Content-Type","name":"Content-Type","value":"application/json","description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","type":"text"}],"body":{"mode":"raw","raw":"{\r\n \"orderTrackingCode\": \"987a9sd8f7a9sd8f7\",\r\n \"userComments\": \"Well, we seem to have made the comment length too much for the API endpoint to swallow, so we need to reduce this down to less than 2000 characters. Here’s some padding to highlight what 2001 characters looks like 78901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901 makes 2001\"\r\n}","options":{"raw":{"language":"json"}}},"url":"https://apistaging.rapidlei.com/v1/leis/uploadComments"},"status":"Bad Request","code":400,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\r\n \"orderStatus\": \"invalid_request\",\r\n \"message\": \"Parameter 'userComments' should not be greater than 2000 characters.\",\r\n \"errorUri\": \"https://rapidlei.com/api\"}\r\n"},{"id":"6c9e7388-2408-4a93-a6d5-ba1c2c276e78","name":"Unsuccessful Response – invalid 'orderTrackingCode'","originalRequest":{"method":"POST","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"key":"Content-Type","name":"Content-Type","value":"application/json","description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","type":"text"}],"body":{"mode":"raw","raw":"{\r\n \"orderTrackingCode\": \"Mycode\",\r\n \"userComments\": \"Page 10 of the annual report details the level 2 parental structure your vetting team needs\"\r\n}","options":{"raw":{"language":"json"}}},"url":"https://apistaging.rapidlei.com/v1/leis/uploadComments"},"status":"Bad Request","code":400,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\r\n \"orderStatus\": \"invalid_request\",\r\n \"message\": \" Invalid Tracking Code - please contact our support team quoting your order tracking code, which can be found in the GUI interface, by clicking on the ‘Enhanced Detail’ from the LEI list. \",\r\n \"errorUri\": \"https://rapidlei.com/api\"\r\n}"}],"_postman_id":"81c095a5-2bf9-4f35-90db-ab43ecb74b3f"},{"name":"LEI – Renew LEI","id":"d8040bd4-3a2f-4fdd-ac6f-675b72f5c57f","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.
\n","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity.
\n","key":"Content-Type","name":"Content-Type","type":"text","value":"application/json"}],"body":{"mode":"raw","raw":"{\r\n \"leiNumber\": \"98450024FD4543302F20\",\r\n \"isLevel1DataSame\": true,\r\n \"notificationUrl\": \"https://www.someotherserver.com/notify/me/when/lei/is/ready\",\r\n \"notificationToken\": \"Sq31YkqGWKXGEpeJGZwM\"\r\n}","options":{"raw":{"language":"json"}}},"url":"https://apistaging.rapidlei.com/v1/leis/orders/renew","description":"This API endpoint initiates the workflow process to move the ‘nextRenewalDate’ forward by 1 year. Renewal is defined as the process to verify all Level 1 & Level 2 data remains accurate on an annual basis. All LEIs not in the final year of a contract will automatically attempt renewal. Only during the last 60 days of the final year of the contract may the contract for an LEI be renewed using this API endpoint. A full list of LEIs can be obtained using the “LEI – Query Renewable LEIs” endpoint. Note that LEIs cannot be renewed unless they have either LAPSED (i.e. outside of any contract) or they are in an ISSUED state and have a ‘nextRenewalDate’ which falls within 60 days of the renewal API call.
\nleiNumberLEI Number for the Legal Entity. e.g. 98450024FD4543302F20
\nisLevel1DataSame
A Boolean value – to agree that the current LE-RD (Level 1) data is the same as the previous year. LE-RD (Level 1 data for any LEI under the management of RapidLEI can be verified using the ‘Query Level 1 LE-RD and Signing Authority’ endpoint
notificationUrlTo avoid unnecessary polling, webhooks can be used to pass orderStatus information in real time. A webhook is a user-defined HTTP (ideally HTTPS) endpoints which can accept POST requests for real time synchronous LEI processing. An optional security token may be used to avoid replay attacks, however the notificationUrl may also contain additional URL parameters. Webhook ApS in Denmark, ran by Simon Fredsted, offers a very simple listening service for testing webhooks. Please see https://webhook.site/ for details and usage guidelines. The two parameters returned in the RequestBody are - orderTrackingCode and orderStatus, with the optional security token being returned as notificationTokene.g. https://www.someotherserver.com/notify/me/when/lei/is/ready
or https://www.someotherserver.com/notify/me/when/lei/is/ready?type=exampletype&token=URL_based_token_examplePLEASE NOTE - Redirects are not guaranteed to be supported in all cases therefore please ensure the correct URL and any final / characters in the URL are sent.
notificationTokenAn optional unique token to avoid the possibility of a third party accidentally making a call to a static notification URL and therefore maliciously affecting the workflow.
e.g. Sq31YkqGWKXGEpeJGZwM\"
userCommentsAn optional comment or instruction to aid efficient processing of the LEI by the RapidLEI vetting team – to be used primarily for simple comments < 1000 characters to avoid the need to send additional corroborating documents.
\nfirstNameThe First Name(s) of the Authorised Representative with the responsibility/authority to request and approve the creation of an LEI e.g. Peter. Only send this if the signing authority has changed in the last year.
\nlastNameThe Last Name of the Authorised Representative e.g. Anderson. Only send this if the signing authority has changed in the last year.
\nmultiYearSupportAn integer from 1 to 5. Please see https://rapidlei.com/lei-pricing/ for details. Please default to 1 as the standard option.
\nloaFile
\nA Letter of Authorization (LoA) is used to provide linkage bewteen the Applicant applying for the LEI and the empowered Authorised Representative name submitted as firstName lastName parameters. LoA's are optional as they can be replaced with appropriate Terms & Conditions. It is usual for a Registration Agent to provide T's and C's which negate the need for an LoA, however, in lieu of these being available, an LoA would be required to provide permission to the Registration Agent from the Empowered Authorised Representative. For more details please discuss with our legal team legal(a)rapidlei.com. Only 1 LoA may be submitted using either the fileData method or fileUrl method.
\ncorroboratingFiles
Up to 10 additional files which may aid vetting or validation of the Application. Please note the upload limit of 20MB each.
The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.
\n","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"key":"Content-Type","value":"application/json","description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity.
\n","type":"text"}],"url":"https://apistaging.rapidlei.com/v1/lei/orders/{orderTrackingCode}/status","description":"This API endpoint is used to check the LEI orderStatus. The bearer access Token from 'Authentication - Request Access Token' is required to submit the request and a valid 'orderTrackingCode' must be submitted within in the URL.
\nfailure\n Sent when unable to process the requested action. See message for additional details as responses vary dependent on the workflow.
\nsuccess\n Sent when actionable. Additional responses dependent on the workflow. e.g. orderTrackingCode & confidenceLevel sent in response to a successful 'New LEI' request.
\nin_progress\n The order is with RapidLEI to progress (gather data, confirm information etc)
\nstopped\n No further action can take place.
\ncomplete\n The workflow is complete. Additional responses dependent on the workflow. e.g. \"message\" & \"leiCode\" returned in response to a successfully issued, imported or renewed LEI
\npending\n LEI Confirm LE-RD Data Quality required by API
\npending_gui\n Confirmation required or additional information required – only possible via the GUI interface
\ninvalid_request\n This message is returned when mandatory parameters are missing
\nauthorization_error\n This message is returned if there's a failure due to either an invalid client_id (email address) or client_secret (API key from My Settings)
\nnot_found\n This message is returned if there's an error in the requested URL
\nunsupported_grant_type\n This message is returned when the underlying protocol for bearer tokens is not used correctly.
\nserver_error\n This message is returned when there is an unexpected issue with the workflow or permission as opposed to a missing parameter
\nThe Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.
\n","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity.
\n","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://apistaging.rapidlei.com/v1/lei/orders/{orderTrackingCode}/confirmation/{orderConfirmationStatus}","description":"This API call is used to confirm the LE-RD data quality status before an LEI can be issued. Set the correct 'orderTrackingCode' in the URL before making an API call. Also make sure you are passing either true or false while replacing the 'orderConfirmationStatus' parameter in the URL.
\nThis API call is one of the most important calls. The call is used to confirm the acceptance of the LE-RD (Legal Entity Reference Data) returned through the 'LEI - Check LEI Order status'. A Legal Entity must be presented with the LE-RD and MUST confirm the accuracy of the data. The Access Token from 'Authentication - Request Access Token' is required to submit the request and the acceptance by the Legal Entity is either 'True' - i.e. The Legal Entity agrees to and accepts the LE-RD or 'False' - i.e. There is an error which must be corrected. It is suggested that a feedback form is used to obtain details of the error. Submitting 'False' requires follow up via the RapidLEI Identity Platform GUI. Submitting 'True' requires the use of the 'LEI - Check LEI Order Status' to obtain the LEI Number.
\n","urlObject":{"protocol":"https","path":["v1","lei","orders","{orderTrackingCode}","confirmation","{orderConfirmationStatus}"],"host":["apistaging","rapidlei","com"],"query":[],"variable":[]}},"response":[{"id":"4a33912f-eed1-47a2-80f6-6691742dca95","name":"Successful Response - Data Quality Confirmation ‘false’","originalRequest":{"method":"POST","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"}],"url":"https://apistaging.rapidlei.com/v1/lei/orders/987a9sd8f7a9sd8f7/confirmation/false"},"status":"OK","code":200,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderTrackingCode\": \"987a9sd8f7a9sd8f7\",\n \"orderStatus\": \"stopped\",\n \"message\": \"We have received confirmation of DISAGREEMENT to the LE-RD Data Quality. We are unable to continue processing this order using the API - Please login to the RapidLEI Identity Platform to continue the process via the ‘Pending’ filter.\"\n}"},{"id":"238da2d2-5147-4065-94ce-13e506271379","name":"Successful Response - Data Quality confirmation ‘true’ (Import LEI)","originalRequest":{"method":"POST","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"}],"url":"https://apistaging.rapidlei.com/v1/lei/orders/987a9sd8f7a9sd8f7/confirmation/true"},"status":"OK","code":200,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderTrackingCode\": \"987a9sd8f7a9sd8f7\",\n \"orderStatus\": \"in_progress\",\n \"message\": \"We have received confirmation of AGREEMENT to the LE-RD Data Quality and will continue processing your order. Your LEI will be imported shortly.\"\n}"},{"id":"cbd05f88-1939-4995-8773-6de2eed0d6f4","name":"Successful Response - Data Quality confirmation ‘true’ (New LEI)","originalRequest":{"method":"PUT","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"key":"Content-Type","value":"application/json","description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","type":"text"}],"url":"https://apistaging.rapidlei.com/v1/lei/orders/987a9sd8f7a9sd8f7/confirmation/true"},"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderTrackingCode\": \"987a9sd8f7a9sd8f7\",\n \"orderStatus\": \"in_progress\",\n \"message\": \"We have received confirmation of AGREEMENT to the LE-RD Data Quality and will continue processing your order. Your LEI will be imported shortly.\"\n}"},{"id":"ba1d1203-4b67-4c4e-b56e-9fa8dc5c521c","name":"Unsuccessful Response - LE-RD Data Quality Confirmation already received and processed","originalRequest":{"method":"POST","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"}],"url":"https://apistaging.rapidlei.com/v1/lei/orders/987a9sd8f7a9sd8f7/confirmation/true"},"status":"Internal Server Error","code":500,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\r\n \"orderTrackingCode\": \"987a9sd8f7a9sd8f7\",\r\n \"orderStatus\": \"failure\",\r\n \"message\": \"We've already received the LE-RD confirmation from you for this Legal Entity - if in doubt, please contact our support team quoting your order tracking code, which can be found in the GUI interface, by clicking on the ‘Enhanced Detail’ from the LEI list.\"\r\n}"},{"id":"fcc1f1b1-3b07-42cf-aaad-95c6b42fe6c0","name":"Unsuccessful Response - InComplete Company Profile Loaded","originalRequest":{"method":"PUT","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"key":"Content-Type","value":"application/json","description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","type":"text"}],"url":"https://apistaging.rapidlei.com/v1/lei/orders/987a9sd8f7a9sd8f7/confirmation/true"},"status":"Internal Server Error","code":500,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderTrackingCode\": \"987a9sd8f7a9sd8f7\",\n \"orderStatus\": \"failure\",\n \"message\": \"We have been unable to obtain all data from the business registry, so we are unable to continue processing using the API. Please login to the RapidLEI Identity Platform to continue the process.\"\n}"},{"id":"e268faef-c18b-403b-943d-fa49e5217fd4","name":"Successful Response - Contract terms agreed but LE-RR Level 2 data is required","originalRequest":{"method":"POST","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"}],"url":"https://apistaging.rapidlei.com/v1/lei/orders/987a9sd8f7a9sd8f7/confirmation/true"},"status":"OK","code":200,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{ \r\n \"orderTrackingCode\": \"987a9sd8f7a9sd8f7\", \r\n \"orderStatus\": \"pending\", \r\n \"message\": \"We are unable to continue processing this order using the API - Please login to the RapidLEI Identity Platform to continue the process.\" \r\n}"},{"id":"2c93d4a0-8110-4f2b-8ad3-d8266f1a118e","name":"Unsuccessful Response - Company Profile Not Loaded","originalRequest":{"method":"PUT","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"key":"Content-Type","value":"application/json","description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","type":"text"}],"url":"https://apistaging.rapidlei.com/v1/lei/orders/987a9sd8f7a9sd8f7/confirmation/true"},"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\r\n \"orderTrackingCode\": \"987a9sd8f7a9sd8f7\",\r\n \"orderStatus\": \"failure\",\r\n \"message\": \"Operation not allowed. Please use the Check Order Status API.\"\r\n}"},{"id":"dd63fdd8-3a45-401a-9eb6-cad82c24214c","name":"Unsuccessful Response - 'orderConfirmationStatus' must be true or false","originalRequest":{"method":"POST","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"}],"url":"https://apistaging.rapidlei.com/v1/lei/orders/987a9sd8f7a9sd8f7/confirmation/asdf"},"status":"Bad Request","code":400,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderStatus\": \"invalid_request\",\n \"message\": \"Request parameter 'orderConfirmationStatus' should contain a Boolean value of either 'true' or 'false'\",\n \"errorUri\": \"https://rapidlei.com/api\"\n}"},{"id":"5b266ea3-a649-4b7e-80e6-83d3a8f5cb22","name":"Unsuccessful Response - Unknown error OR Exception during processing request","originalRequest":{"method":"POST","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"}],"url":"https://apistaging.rapidlei.com/v1/lei/orders/987a9sd8f7a9sd8f7/confirmation/true"},"status":"Internal Server Error","code":500,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderStatus\": \"server_error\",\n \"message\": \"We've been unable to process your request - please contact our support team quoting your order tracking code, which can be found in the GUI interface, by clicking on the ‘Enhanced Detail’ from the LEI list.\",\n \"errorUri\": \"https://rapidlei.com/api\"\n}"},{"id":"4d7c0dad-4d0b-4173-88fe-2520fb6ad215","name":"Successful Response – Data Quality Pre–Check and Duplicate API calls are being made to the GLEIS for new LEIs","originalRequest":{"method":"POST","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"}],"url":"https://api.rapidlei.com/v1/lei/orders/987a9sd8f7a9sd8f7/confirmation/true"},"status":"OK","code":200,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\r\n \"orderTrackingCode\": \"987a9sd8f7a9sd8f7\",\r\n \"orderStatus\": \"in_progress\",\r\n \"message\": \" You've submitted the Data Duality Confirmation at the point we are doing a Check for Duplicates (C4D) call to the GLEIS. These can take between 15 and 45 seconds. We've acknowledged your confirmation of the profile accuracy, so you do not need to submit again.\"\r\n}"},{"id":"3ccfd35e-b4a4-4a44-aecd-f690afa65d8d","name":"Successful Response – Data Quality Pre–Check calls are being made to the GLEIS for imported LEIs","originalRequest":{"method":"POST","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"}],"url":"https://api.rapidlei.com/v1/lei/orders/987a9sd8f7a9sd8f7/confirmation/true"},"status":"OK","code":200,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\r\n \"orderTrackingCode\": \"987a9sd8f7a9sd8f7\",\r\n \"orderStatus\": \"in_progress\",\r\n \"message\": \" You've submitted the Data Duality Confirmation at the point we are doing a Check for Duplicates (C4D) call to the GLEIS. These can take between 15 and 45 seconds. We've acknowledged your confirmation of the profile accuracy, so you do not need to submit again.\"\r\n}"}],"_postman_id":"3ee441d0-0104-4182-b167-6299e463d6d4"},{"name":"LEI - Query all LEIs","id":"0dedbc5e-7edd-4640-bc24-f2477610b40f","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"GET","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.
\n","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity.
\n","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://apistaging.rapidlei.com/v1/leis/orders","description":"This API is used to query for a list of ALL LEIs which have been successfully issued (Created or Imported) from the account. This includes shopping cart and XLS based bulk workflows. Any LEI which has not yet been issued, but has been created by API calls can be verified individually by the 'LEI - Check Order Status' call. Any requests made via the shopping cart or xls methods may be tracked from within the browser based UI by logging in to the https://lei.rapidlei.com/Account/Login. The Access Token from 'Authentication - Request Access Token' is required to submit the request.
\nPlease note that this API call DOES NOT return LEI numbers if the LEI has been marked as a DUPLICATE, ANULLED, MERGED or RETIRED.
\nOnly LEIs with a registration status of ISSUED or LAPSED will be returned.
\nReviewing LEI-RD (Reference data) is possible via the LEI number and the GLEIF API call. https://www.gleif.org/en/lei-data/gleif-lei-look-up-api/access-the-api
\n","urlObject":{"protocol":"https","path":["v1","leis","orders"],"host":["apistaging","rapidlei","com"],"query":[],"variable":[]}},"response":[{"id":"09bf80dd-53e7-4341-825e-66b9705c0987","name":"Successful Response – List of LEIs returned","originalRequest":{"method":"GET","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://apistaging.rapidlei.com/v1/leis/orders"},"status":"OK","code":200,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\r\n \"new\": [\r\n \"984500049401E2B8D492\",\r\n \"984500049401E2B8D491\",\r\n \"984500049401E2B8D494\"\r\n ],\r\n \"imported\": [\r\n \"213800MAKC4IOK7LEH11\",\r\n \"213800MAKC4IOK7LEH12\",\r\n \"213800MAKC4IOK7LEH13\"\r\n ]\r\n}"},{"id":"ee540337-d932-496d-822c-fed1fc6e3214","name":"Unsuccessful Response – Unknown Error or Exception during processing request","originalRequest":{"method":"GET","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://apistaging.rapidlei.com/v1/leis/orders"},"status":"Internal Server Error","code":500,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderStatus\": \"server_error\",\n \"message\": \" We've been unable to process your request – please contact our support team.\",\n \"errorUri\": \"https://rapidlei.com/api\"\n}"},{"id":"f41debaf-b6e2-4ffa-a147-b1555f9baa12","name":"Unsuccessful Response – User not allowed to use the Full API, only the ‘Create User’ endpoint","originalRequest":{"method":"GET","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://apistaging.rapidlei.com/v1/leis/orders"},"status":"Unauthorized","code":401,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderStatus\": \"authorization_error\",\n \"message\": \"You do not have the ability to use the Full RapidLEI API from this account – you are configured only to use the ‘Create User’ endpoint, please contact our support team on support@rapidlei.com\",\n \"errorUri\": \"https://rapidlei.com/api\"\n}"}],"_postman_id":"0dedbc5e-7edd-4640-bc24-f2477610b40f"},{"name":"LEI – Query Lapsed LEIs","id":"2cce47d7-d004-4a15-9f00-ef6eb1139011","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"GET","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.
\n","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity.
\n","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://apistaging.rapidlei.com/v1/leis/orders/lapsed","description":"This API call is used to query all LAPSED LEIs.
\n","urlObject":{"protocol":"https","path":["v1","leis","orders","lapsed"],"host":["apistaging","rapidlei","com"],"query":[],"variable":[]}},"response":[{"id":"0a4a9939-6977-487f-ad7b-f8eb48675649","name":"Successful Response – List of LEIs and nextRenewalDate’s returned","originalRequest":{"method":"GET","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://apistaging.rapidlei.com/v1/leis/orders/lapsed"},"status":"OK","code":200,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"[\n {\n \"leiNumber\": \"14955838975411027285\",\n \"nextRenewalDate\": \"2021-07-09T11:54:35+00:00\"\n },\n {\n \"leiNumber\": \"984500EFP7C0E4CEA733\",\n \"nextRenewalDate\": \"2021-07-29T11:54:35+00:00\"\n },\n {\n \"leiNumber\": \"984500801560A0481F75\",\n \"nextRenewalDate\": \"2021-07-09T11:54:35+00:00\"\n }\n]"},{"id":"840670d3-451e-49fc-83b5-24635f060409","name":"Unsuccessful Response – User not allowed to use the Full API, only the ‘Create User’ endpoint","originalRequest":{"method":"GET","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://apistaging.rapidlei.com/v1/leis/orders/lapsed"},"status":"Unauthorized","code":401,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderStatus\": \"authorization_error\",\n \"message\": \"You do not have the ability to use the Full RapidLEI API from this account – you are configured only to use the ‘Create User’ endpoint, please contact our support team on support@rapidlei.com\",\n \"errorUri\": \"https://rapidlei.com/api\"\n}"},{"id":"2ce12fd0-44ff-4f04-b659-5ed238bddbdc","name":"Unsuccessful Response – Unknown Error or Exception during processing request","originalRequest":{"method":"GET","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://apistaging.rapidlei.com/v1/leis/orders/lapsed"},"status":"Internal Server Error","code":500,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderStatus\": \"server_error\",\n \"message\": \" We've been unable to process your request - please contact our support team.\",\n \"errorUri\": \"https://rapidlei.com/api\"\n}"}],"_postman_id":"2cce47d7-d004-4a15-9f00-ef6eb1139011"},{"name":"LEI – Query Renewable LEIs","id":"f10ab59b-9ec4-47ef-89b2-9fdfe6621142","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"GET","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.
\n","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity.
\n","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://apistaging.rapidlei.com/v1/leis/orders/renew/{days}","description":"This API call is used to query all LEIs which may be renewed within the next {days}. The parameter \"days\" is a numeric value between 1 and 60. Ideally values of 15, 30, 45 or 60 are passed to mirror the GUI DASHBOARD Interface. Please note that multi-year LEIs will automatically renew 60 days prior to the “nextRenewalDate” and are therefore excluded from the returned list. The exception being any LEI with Level 2 data or any ESO based FUND which cannot be verified by the RapidLEI vetting team - these will appear too.
\n","urlObject":{"protocol":"https","path":["v1","leis","orders","renew","{days}"],"host":["apistaging","rapidlei","com"],"query":[],"variable":[]}},"response":[{"id":"e3d937af-b101-48f0-88f1-0ee48303a88f","name":"Successful Response – List of LEIs and nextRenewalDate’s returned","originalRequest":{"method":"GET","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://apistaging.rapidlei.com/v1/leis/orders/renew/60"},"status":"OK","code":200,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"[\n {\n \"leiNumber\": \"14955838975411027285\",\n \"nextRenewalDate\": \"2021-07-09T11:54:35+00:00\"\n },\n {\n \"leiNumber\": \"984500EFP7C0E4CEA733\",\n \"nextRenewalDate\": \"2021-07-29T11:54:35+00:00\"\n },\n {\n \"leiNumber\": \"984500801560A0481F75\",\n \"nextRenewalDate\": \"2021-07-09T11:54:35+00:00\"\n }\n]"},{"id":"e591093c-6d20-4702-b180-15ea5133dbee","name":"Unsuccessful Response – User not allowed to use the Full API, only the ‘Create User’ endpoint","originalRequest":{"method":"GET","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://apistaging.rapidlei.com/v1/leis/orders/renew/60"},"status":"Unauthorized","code":401,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderStatus\": \"authorization_error\",\n \"message\": \"You do not have the ability to use the Full RapidLEI API from this account – you are configured only to use the ‘Create User’ endpoint, please contact our support team on support@rapidlei.com\",\n \"errorUri\": \"https://rapidlei.com/api\"\n}"},{"id":"69d34bde-311d-4e45-849c-28ff17a284df","name":"Unsuccessful Response – Unknown Error or Exception during processing request","originalRequest":{"method":"GET","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://apistaging.rapidlei.com/v1/leis/orders/renew/60"},"status":"Internal Server Error","code":500,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderStatus\": \"server_error\",\n \"message\": \" We've been unable to process your request - please contact our support team.\",\n \"errorUri\": \"https://rapidlei.com/api\"\n}"},{"id":"0f39d662-064c-4196-820d-29aca65ddbf0","name":"Unsuccessful Response – Invalid or nonnumeric days parameter","originalRequest":{"method":"GET","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://apistaging.rapidlei.com/v1/leis/orders/renew/100"},"status":"Bad Request","code":400,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderStatus\": \"invalid_request\",\n \"message\": \"Request parameter ‘days’ should contain a numeric value between 1 and 60\",\n \"errorUri\": \"https://rapidlei.com/api\"\n}"}],"_postman_id":"f10ab59b-9ec4-47ef-89b2-9fdfe6621142"},{"name":"LEI – Query Level 1 LE-RD and Authorised Representative","id":"ae6f165b-a711-42ab-ab52-1cf993674814","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"GET","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.
\n","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity.
\n","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://apistaging.rapidlei.com/v1/leis/level1/{leiNumber}","description":"This API call is used to query Level 1 (LE-RD) data for any LEI managed by RapidLEI
\n","urlObject":{"protocol":"https","path":["v1","leis","level1","{leiNumber}"],"host":["apistaging","rapidlei","com"],"query":[],"variable":[]}},"response":[{"id":"5fdf4d5e-6395-4a89-bc58-dbeb3ed8ff46","name":"Successful Response – LEI Level 1 LE-RD and Authorised Representative data available","originalRequest":{"method":"GET","header":[{"key":"Authorization","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx","description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","type":"text"},{"key":"Content-Type","value":"application/json","description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","type":"text"}],"url":"https://apistaging.rapidlei.com/v1/leis/level1/529900T8BM49AURSDO55"},"status":"OK","code":200,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"signingAuthorityName\": \"Paul Tourret\",\n \"referenceData\": {\n \"leiNumber\": \"529900T8BM49AURSDO55\",\n \"legalName\": \"Ubisecure Oy\",\n \"legalNameLanguage\": \"fi\",\n \"registrationAuthorityEntityId\": \"1748721–4\",\n \"entityLegalFormCode\": \"DKUW\",\n \"entityLegalForm\": null,\n \"entityLegalFormLanguage\": \"FI\",\n \"entityStatus\": \"ACTIVE\",\n \"registrationAuthorityId\": \"RA000188\",\n \"registrationAuthority\": null,\n \"entityCategory\": \"GENERAL\",\n \"entityCreationDate\" : \"2002-02-14T00:00:00+00:00\",\n \"legalJurisdiction\": \"FI\",\n \"initialRegistrationDate\": \"2016–08–04T11:00:36+00:00\",\n \"nextRenewalDate\": \"2025–12–20T12:23:13+00:00\",\n \"lastUpdateDate\": \"2024–12–20T12:23:13+00:00\",\n \"registrationStatus\": \"ISSUED\",\n \"validationSource\": \"FULLY_CORROBORATED\",\n \"managingLOU\": \"529900T8BM49AURSDO55\",\n \"successorLEI\": null,\n \"successorEntityName\": null,\n \"contractExpiryDate\": \"2028-01-21T21:54:37+00:00\",\n \"otherEntityNames\": [\n {\n \"type\": \"TRADING_OR_OPERATING_NAME\",\n \"value\": \"Ubisecure Inc\",\n \"language\": \"FI\"\n },\n {\n \"type\": \"TRADING_OR_OPERATING_NAME\",\n \"value\": \"Ubisecure Ab\",\n \"language\": \"SV\"\n }\n ],\n \"transliteratedOtherEntityNames\": [],\n \"legalAddress\": {\n \"mailRouting\": null,\n \"firstAddressLine\": \"Vaisalantie 2\",\n \"addressLine1\": null,\n \"addressLine2\": null,\n \"addressLine3\": null,\n \"city\": \"Espoo\",\n \"state\": null,\n \"country\": \"FI\",\n \"postalCode\": \"02130\"\n },\n \"transliertatedLegalAddress\": null,\n \"headquartersAddress\": {\n \"mailRouting\": null,\n \"firstAddressLine\": \"Tekniikantie 14\",\n \"addressLine1\": null,\n \"addressLine2\": null,\n \"addressLine3\": null,\n \"city\": \"Espoo\",\n \"state\": null,\n \"country\": \"FI\",\n \"postalCode\": \"02150\"\n },\n \"transliteratedHeadquartersAddress\": null,\n \"validationAuthority\": {\n \"validationAuthorityID\": \"RA000188\",\n \"otherValidationAuthorityID\": null,\n \"validationAuthorityEntityID\": \"1748721–4\"\n },\n \"otherValidationAuthorities\": []\n }\n} "},{"id":"5e36e26c-2943-4119-9182-b6956ac762d1","name":"Unsuccessful Response – LEI not managed by your RapidLEI account","originalRequest":{"method":"GET","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://apistaging.rapidlei.com/v1/leis/level1/529900T8BM49AURSDO55"},"status":"Internal Server Error","code":500,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderStatus\": \"failure\",\n \"message\": \"The LEI number requested is not managed by your RapidLEI account. Please provide a valid LEI Number or contact our support team to discuss options.\"\n}"},{"id":"7ab2b007-01b0-4515-b9d1-0d81cdd4fabf","name":"Unsuccessful Response – Level 1 data is not currently available","originalRequest":{"method":"GET","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://apistaging.rapidlei.com/v1/leis/level1/529900T8BM49AURSDO55"},"status":"Internal Server Error","code":500,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderStatus\": \"failure\",\n \"message\": \" The LEI must be either ISSUED, LASPED, DUPLICATE, PENDING_TRANSFER, PENDING_ARCHIVAL, RETIRED or MERGED for level 1 data to be available. LEIs which are ‘pending’, ‘pending_gui’ or ‘in_progress’ may not be queried.\"\n}"},{"id":"23455b4d-dc19-4017-a73e-bb1592df236a","name":"Unsuccessful Response – Invalid LEI Format","originalRequest":{"method":"GET","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://apistaging.rapidlei.com/v1/leis/level1/529900T8BM49A"},"status":"Bad Request","code":400,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderStatus\": \"invalid_request\",\n \"message\": \"Please ensure the 'lei' is a valid ISO 17442 format LEI (20 characters).\",\n \"errorUri\": \"https://rapidlei.com/api\"\n}"},{"id":"384059d0-2d09-4b3a-96d0-e597e3f39f1e","name":"Unsuccessful Response – User not allowed to use the Full API, only the ‘Create User’ endpoint","originalRequest":{"method":"GET","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://apistaging.rapidlei.com/v1/leis/level1/529900T8BM49AURSDO55"},"status":"Unauthorized","code":401,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderStatus\": \"authorization_error\",\n \"message\": \"You do not have the ability to use the Full RapidLEI API from this account – you are configured only to use the ‘Create User’ endpoint, please contact our support team on support@rapidlei.com\",\n \"errorUri\": \"https://rapidlei.com/api\"\n}"},{"id":"aa39d499-bbec-46c4-a468-fbc7bbd777c8","name":"Unsuccessful Response – Unknown Error or Exception during processing request","originalRequest":{"method":"GET","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://apistaging.rapidlei.com/v1/leis/level1/529900T8BM49AURSDO55"},"status":"Internal Server Error","code":500,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderStatus\": \"server_error\",\n \"message\": \" We've been unable to process your request - please contact our support team.\",\n \"errorUri\": \"https://rapidlei.com/api\"\n}"}],"_postman_id":"ae6f165b-a711-42ab-ab52-1cf993674814"},{"name":"LEI – Query Level 2 LE-RR, LE-RE and PNI data","id":"56e89359-cbc0-4ee2-89f6-93e89e8c7b6e","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"GET","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.
\n","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity.
\n","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://apistaging.rapidlei.com/v1/leis/level2/{leiNumber}","description":"This API call is used to query Level 2 (LE-RR) data for any LEI managed by RapidLEI. This includes, relationship data, exception reporting and if level 2 parents do not have LEIs, PNI data.
\n","urlObject":{"protocol":"https","path":["v1","leis","level2","{leiNumber}"],"host":["apistaging","rapidlei","com"],"query":[],"variable":[]}},"response":[{"id":"db02ca0c-02b7-4cfa-94c0-1a0bcc9d3379","name":"Successful Response – Level 2 data has Reporting Exceptions ","originalRequest":{"method":"GET","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://apistaging.rapidlei.com/v1/leis/level2/984500B8IBDAB46C3750"},"status":"OK","code":200,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"relationshipRecords\": [],\n \"reportingExceptions\": [\n {\n \"lei\": \"984500B8IBDAB46C3750\",\n \"exceptionCategory\": \"DIRECT_ACCOUNTING_CONSOLIDATION_PARENT\",\n \"exceptionReason\": \"NATURAL_PERSONS\",\n \"exceptionReference\": null\n },\n {\n \"lei\": \"984500B8IBDAB46C3750\",\n \"exceptionCategory\": \"ULTIMATE_ACCOUNTING_CONSOLIDATION_PARENT\",\n \"exceptionReason\": \"NATURAL_PERSONS\",\n \"exceptionReference\": null\n }\n ],\n \"parentReferenceRecords\": []\n}"},{"id":"93bb5c25-7011-4707-88b1-92587f3ec6a3","name":"Successful Response – Level 2 data has Relationship Records","originalRequest":{"method":"GET","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://apistaging.rapidlei.com/v1/leis/level2/984500B8IBDAB46C3750"},"status":"OK","code":200,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"relationshipRecords\": [\n {\n \"startNode\": {\n \"nodeID\": \"529900T8BM49AURSDO55\",\n \"nodeIDType\": \"LEI\"\n },\n \"endNode\": {\n \"nodeID\": \"89450051ZRDOL9KEWH63\",\n \"nodeIDType\": \"LEI\"\n },\n \"relationshipType\": \"IS_DIRECTLY_CONSOLIDATED_BY\",\n \"relationshipStatus\": \"ACTIVE\",\n \"initialRegistrationDate\": \"2018-05-08T18:15:52+00:00\",\n \"lastUpdateDate\": \"2021-02-20T12:23:13+00:00\",\n \"nextRenewalDate\": \"2022-12-20T12:23:13+00:00\",\n \"registrationStatus\": \"PUBLISHED\",\n \"managingLOU\": \"529900T8BM49AURSDO55\",\n \"validationSources\": \"FULLY_CORROBORATED\",\n \"validationDocuments\": \"ACCOUNTS_FILING\",\n \"validationReference\": null,\n \"relationshipQualifier\": {\n \"qualifierDimension\": \"ACCOUNTING_STANDARD\",\n \"qualifierCategory\": \"OTHER_ACCOUNTING_STANDARD\"\n },\n \"relationshipQuantifier\": {\n \"measurementMethod\": \"ACCOUNTING_CONSOLIDATION\",\n \"quantifierAmount\": 100,\n \"quantifierUnits\": \"PERCENTAGE\"\n },\n \"relationshipPeriods\": [\n {\n \"startDate\": \"2021-01-01T00:00:00+00:00\",\n \"endDate\": \"2021-12-31T00:00:00+00:00\",\n \"periodType\": \"ACCOUNTING_PERIOD\"\n },\n {\n \"startDate\": \"2018-05-17T00:00:00+00:00\",\n \"endDate\": null,\n \"periodType\": \"RELATIONSHIP_PERIOD\"\n }\n ]\n },\n {\n \"startNode\": {\n \"nodeID\": \"529900T8BM49AURSDO55\",\n \"nodeIDType\": \"LEI\"\n },\n \"endNode\": {\n \"nodeID\": \"89450051ZRDOL9KEWH63\",\n \"nodeIDType\": \"LEI\"\n },\n \"relationshipType\": \"IS_ULTIMATELY_CONSOLIDATED_BY\",\n \"relationshipStatus\": \"ACTIVE\",\n \"initialRegistrationDate\": \"2018-05-08T18:15:52+00:00\",\n \"lastUpdateDate\": \"2021-02-20T12:23:13+00:00\",\n \"nextRenewalDate\": \"2022-12-20T12:23:13+00:00\",\n \"registrationStatus\": \"PUBLISHED\",\n \"managingLOU\": \"529900T8BM49AURSDO55\",\n \"validationSources\": \"FULLY_CORROBORATED\",\n \"validationDocuments\": \"ACCOUNTS_FILING\",\n \"validationReference\": null,\n \"relationshipQualifier\": {\n \"qualifierDimension\": \"ACCOUNTING_STANDARD\",\n \"qualifierCategory\": \"OTHER_ACCOUNTING_STANDARD\"\n },\n \"relationshipQuantifier\": {\n \"measurementMethod\": \"ACCOUNTING_CONSOLIDATION\",\n \"quantifierAmount\": 100,\n \"quantifierUnits\": \"PERCENTAGE\"\n },\n \"relationshipPeriods\": [\n {\n \"startDate\": \"2021-01-01T00:00:00+00:00\",\n \"endDate\": \"2021-12-31T00:00:00+00:00\",\n \"periodType\": \"ACCOUNTING_PERIOD\"\n },\n {\n \"startDate\": \"2018-05-17T00:00:00+00:00\",\n \"endDate\": null,\n \"periodType\": \"RELATIONSHIP_PERIOD\"\n }\n ]\n }\n ],\n \"reportingExceptions\": [],\n \"parentReferenceRecords\": []\n}"},{"id":"91b0f6a8-c536-4ce1-bad5-195c7ec449b7","name":"Successful Response – Level 2 data has Parent Reference Data (PNI) ","originalRequest":{"method":"GET","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://apistaging.rapidlei.com/v1/leis/level2/984500B8IBDAB46C3750"},"status":"OK","code":200,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"relationshipRecords\": [],\n \"reportingExceptions\": [\n {\n \"lei\": \"984500B8IBDAB46C3750\",\n \"exceptionCategory\": \"DIRECT_ACCOUNTING_CONSOLIDATION_PARENT\",\n \"exceptionReason\": \"NO_LEI\",\n \"exceptionReference\": null\n },\n {\n \"lei\": \"984500B8IBDAB46C3750\",\n \"exceptionCategory\": \"ULTIMATE_ACCOUNTING_CONSOLIDATION_PARENT\",\n \"exceptionReason\": \"NO_LEI\",\n \"exceptionReference\": null\n }\n ],\n \"parentReferenceRecords\": [\n {\n \"legalName\": \"UBISECURE HOLDINGS LIMITED\",\n \"registrationAuthorityEntityId\": \"10408185\",\n \"legalJurisdiction\": \"GB–ENG\",\n \"parentType\": \"DIRECT_PARENT\"\n },\n {\n \"legalName\": \"UBISECURE HOLDINGS LIMITED\",\n \"legalNameLanguage\": \"en\",\n \"registrationAuthorityEntityId\": \"10408185\",\n \"legalJurisdiction\": \"GB–ENG\",\n \"parentType\": \"ULTIMATE_PARENT\"\n }\n ]\n}"},{"id":"d048c2d9-6339-4cef-af90-6fadc3d07147","name":"Successful Response – Level 2 Fund Reporting","originalRequest":{"method":"GET","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://apistaging.rapidlei.com/v1/leis/level2/984500B8IBDAB46C3750"},"status":"OK","code":200,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"relationshipRecords\": [\n {\n \"startNode\": {\n \"nodeID\": \"529900T8BM49AURSDO55\",\n \"nodeIDType\": \"LEI\"\n },\n \"endNode\": {\n \"nodeID\": \"89450051ZRDOL9KEWH63\",\n \"nodeIDType\": \"LEI\"\n },\n \"relationshipType\": \"IS_FEEDER_TO\",\n \"relationshipStatus\": \"ACTIVE\",\n \"initialRegistrationDate\": \"2021–12–20T12:23:13+00:00\",\n \"lastUpdateDate\": \"2021–12–20T12:23:13+00:00\",\n \"nextRenewalDate\": \"2022–12–20T12:23:13+00:00\",\n \"registrationStatus\": \"PUBLISHED\",\n \"managingLOU\": \"529900T8BM49AURSDO55\",\n \"validationSources\": \"ENTITY_SUPPLIED_ONLY\",\n \"validationDocuments\": \"ACCOUNTS_FILING\",\n \"validationReference\": \"https://www.fund-data-reference-example.com\",\n \"relationshipPeriods\": [\n {\n \"startDate\": \"2020-01-14T00:00:00+00:00\",\n \"endDate\": null,\n \"periodType\": \"RELATIONSHIP_PERIOD\"\n }\n ]\n }\n ],\n \"reportingExceptions\": [\n {\n \"lei\": \"529900T8BM49AURSDO55\",\n \"exceptionCategory\": \"DIRECT_ACCOUNTING_CONSOLIDATION_PARENT\",\n \"exceptionReason\": \"NON_CONSOLIDATING\",\n \"exceptionReference\": null\n },\n {\n \"lei\": \"529900T8BM49AURSDO55\",\n \"exceptionCategory\": \"ULTIMATE_ACCOUNTING_CONSOLIDATION_PARENT\",\n \"exceptionReason\": \"NON_CONSOLIDATING\",\n \"exceptionReference\": null\n }\n ],\n \"parentReferenceRecords\": []\n}"},{"id":"6abf3de5-776d-4bd7-86b9-23d3a36e645f","name":"Unsuccessful Response – LEI not managed by your RapidLEI account","originalRequest":{"method":"GET","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://apistaging.rapidlei.com/v1/leis/level2/984500B8IBDAB46C3750"},"status":"Internal Server Error","code":500,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderStatus\": \"failure\",\n \"message\": \"The LEI number requested is not managed by your RapidLEI account. Please provide a valid LEI Number or contact our support team to discuss options.\"\n}"},{"id":"39834c0d-edcb-4cae-8e1c-f1902003b46b","name":"Unsuccessful Response – Level 2 data is not currently available","originalRequest":{"method":"GET","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://apistaging.rapidlei.com/v1/leis/level2/984500B8IBDAB46C3750"},"status":"Internal Server Error","code":500,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderStatus\": \"failure\",\n \"message\": \" The LEI must be either ISSUED, LASPED, DUPLICATE, PENDING_TRANSFER, PENDING_ARCHIVAL, RETIRED or MERGED for level 2 data to be available. LEIs which are ‘pending’, ‘pending_gui’ or ‘in_progress’ may not be queried.\"\n}"},{"id":"5981faa8-b7b1-47c5-b599-09bec14f7515","name":"Unsuccessful Response – Invalid LEI Format","originalRequest":{"method":"GET","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://apistaging.rapidlei.com/v1/leis/level2/984500B8"},"status":"Bad Request","code":400,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderStatus\": \"invalid_request\",\n \"message\": \"Please ensure the 'lei' is a valid ISO 17442 format LEI (20 characters).\",\n \"errorUri\": \"https://rapidlei.com/api\"\n}"},{"id":"b608ea81-5c53-4d4d-abf2-01096d8419d8","name":"Unsuccessful Response – User not allowed to use the Full API, only the ‘Create User’ endpoint","originalRequest":{"method":"GET","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://apistaging.rapidlei.com/v1/leis/level2/984500B8IBDAB46C3750"},"status":"Unauthorized","code":401,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderStatus\": \"authorization_error\",\n \"message\": \"You do not have the ability to use the Full RapidLEI API from this account – you are configured only to use the ‘Create User’ endpoint, please contact our support team on support@rapidlei.com\",\n \"errorUri\": \"https://rapidlei.com/api\"\n}"},{"id":"ec0cb3fe-e26b-4f93-b6fe-de8f8e23e84a","name":"Unsuccessful Response – Unknown Error or Exception during processing request","originalRequest":{"method":"GET","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://apistaging.rapidlei.com/v1/leis/level2/984500B8IBDAB46C3750"},"status":"Internal Server Error","code":500,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderStatus\": \"server_error\",\n \"message\": \" We've been unable to process your request - please contact our support team.\",\n \"errorUri\": \"https://rapidlei.com/api\"\n}"}],"_postman_id":"56e89359-cbc0-4ee2-89f6-93e89e8c7b6e"}],"id":"c3185149-fd4d-4156-8e98-839fb2c33bfa","description":"Version - September 2025
\nRapidLEI API endpoints have been designed to facilitate efficient workflows enabling Registration Agents, Validation Agents, and Enterprise's to 'Create New LEIs', 'Import Existing LEIs' or 'Renew LEIs'.
\nWith the exception of 'API Health Check', which requires no Authentication, RFC 6750 OAuth 2.0 Bearer Token Authentication is used in all cases. API Key(s) used to create Bearer Token(s) via the 'Authentication - Request Access Token' endpoint are managed in 'My Settings' in RapidLEI accounts with extended privileges.
\nFor access credentials please speak to our team on partnerships@rapidlei.com.
\nThese API(s) rely on access being granted to the RapidLEI Staging platform - a test facility offering real time connectivity to several (but not all) business registry's in order to optimize API issuance workflows. For access credentials please speak to our team on partnerships@rapidlei.com.
\nThe RapidLEI API is designed to avoid unnecessary polling. Whenever possible, please use the built-in 'Push Notifications' system (Details given below). Status updates, enabling polling logic workflow optimizations, are returned via the orderStatus token, whereas optional, human readable feedback from the vetting team on why an LEI order has paused is available from the adminMessage token e.g. *\"The Business Registry is currently offline – We are unable to continue processing this order until it reopens.\"*
\nin_progress
The order is with RapidLEI to progress (gather data, confirm information etc)
stopped
No further action can take place.
complete
The workflow is complete. Additional responses dependent on the workflow. e.g. \"message\" & \"leiCode\" returned in response to a successfully issued, imported or renewed LEI
pending
LEI Confirm LE-RD Data Quality required by API
pending_gui
Confirmation required or additional information required – only possible via the GUI interface
invalid_request
This message is returned when mandatory parameters are missing
authorization_error
This message is returned if there's a failure due to either an invalid client_id (email address) or client_secret (API key from My Settings)
not_found
This message is returned if there's an error in the requested URL
unsupported_grant_type
This message is returned when the underlying protocol for bearer tokens is not used correctly.
server_error
This message is returned when there is an unexpected issue with the workflow or permission as opposed to a missing parameter
Push Notifications, aka webhooks are *\"user-defined callbacks made with HTTP\"* (ideally HTTPS) endpoints which can accept POST requests. An optional security token may be used to avoid replay attacks, however the notificationUrl may also contain additional URL parameters. Webhook ApS in Denmark, ran by Simon Fredsted, offers a very simple listening service for testing webhooks. Please see https://webhook.site/ for details and usage guidelines.
The two parameters returned in the RequestBody are - orderTrackingCode and orderStatus, with the optional security token being returned as notificationToken within the Header.
profile_loaded
Sent as soon as our platform obtains the profile from the business registry. In the event of a failure, or an incomplete profile being received, our vetting team adds the missing items the registry did not provide and at this point we send profile_loaded. This can be minutes or hours depending on the jurisdiction/registry. Please use 'LEI - Check Order Status' to verify the profile's accuracy. Either verify the returned profile against data previously provided by the Applicant, or use this data to confirm the accuracy with the Applicant in a post processing workflow.
lei_issued
Sent once the LEI is ISSUED and all checks are complete including the Authority Check. (Please note that we do not send a notification for a ‘Pre-Authority LEI number’). Please use 'LEI - Check Order Status' to obtain the LEI number and the nextRenewalDate.
lei_imported
Sent once the LEI is IMPORTED and all checks are complete including the Authority Check. Please use 'LEI - Check Order Status' to obtain the LEI number and the nextRenewalDate.
lei_cancelled
Sent after a cancellation from either our Admin team or the GUI interface. (Cancellation by API is not supported)
lei_pending_gui
Sent once an edge case is identified and control is returned to the GUI Interface.
lei_duplicate_found
A potential Duplicate has been identified by a GLEIF API call and our team are investigating.
lei_pre_check_api
A pre–check API call to GLEIF has failed – RapidLEI will be investigating and correcting any issues.
lei_renewed
Sent once the LEI is renewed and all checks are complete. Please use 'LEI - Check Order Status' to obtain the LEI number and the nextRenewalDate.
lei_published
Sent once the LEI has been successfully uploaded to the GLEIS during one of the 10 daily publication cycles. For a new LEI, or changes to an existing LEI to be visible, additional time must be allowed for the GLEIF to process the data and publish to the Concatenated files, Golden Copy files & LEI Search 2.0 system – this ranges between 2 and 8 hours of our publication time.
lou_import_requested
Sent when the request to the SENDING LOU has been made. The SENDING_LOU, in response, should flip the GLEIF LEI Status from ISSUED/LASPED to PENDING_TRANSFER within 3 days indicating the request is received and that they are talking to their client.
lou_import_request_acknowledged
Sent when the GLEIF LEI Status flips to PENDING_TRANSFER. The SENDING_LOU then has 4 days to confirm the acceptance or rejection of the request.
lou_rejected
Sent after receiving a rejection from the SENDING LOU during transfer by a GLEIF LEI Status change back to LASPED/ISSUED.
lei_transferred
Sent after an LEI has successfully been transferred. i.e from RapidLEI (as the Sending LOU) to the Receiving LOU. This status will only appear when the Receiving LOU publishes the LEI to the GLEIS.
The maximum allowed FileName length (including an extension) = 250 characters e.g. \"FileName\":\"This is an example file name which shows the extent possible within the RapidLEI API eco system for Ubisecure Oy with LEI Code 529900T8BM49AURSDO55 - The remaining characters up to 250 being these... 4567890123456789012345678901234567890123456789.pdf”
\nThe maximum allowed FileURL length (including an extension) = 1000 characters e.g. \"FileURL\":\"https://someexamplefileserver.com/attachements/rapidlei/ BNVcyW5rbFdjYzAwekdONHhMU1hMbFBoWFV0bXBra2FuQ1dzUWVMYWoyRUJoU3huRFhpZnVENExhaERBNVcyWkpVTk9YcHBjT1lFK2xvUW5rbFdjYzAwekdONHhMU1hMbFBoWFV0bXBra2FuQ1dzUWVMYWoyRUJoU3huRFhpZnVEVkscHBjT1l1FK2xvUW5rb5FERBNVcyWkpVTk9YcHBjT1lFK2xvUW5rbFdjYzAwekdONHhMU1hMbFBoWFV0bXBra2FuQ1dzUWVMYWoyRUJoUhuRFhpZnVEyZE9WNGJtQUhMM2lSZ1JWXVzWldKaUROeThadVONVVNUlJ3N3NFVFJZMwkpVTk9YcHBjT1lF2xvUW5rbFdjYzAwekdONHhMU1hMbFBoWFV0bXBra2FuQ1dzUWVMYWoyRUJS2dBOU9Z4cHBjT1lFK2xvUW5rbFdjYzAwekdONHhMU1hMbFBoWFV0bXBra772Fu1dzUWVMYWoyRUJS2dBOUZ4NExhaERBNVcykpVTk9YcHBjT1lFK2xvUW5rbFdjYzAwekdONHhMU1hMbFBoWFV0bXBra2FuQ1dzUWVMYWoyRUJoUhuRFhpZnVENExhaERBNVcyWkpVTk9YcHBjT1lFK2xvUW5rbFdjYzAwekdONHhMU1hMbFBoWFV0bXBra2FuQ1dzUWVMYWoyRUJU3huRFhpZnVEVkscHBjT1lFK2xvUW5rbFdjYzAwekdONHhMU1hMbFBoWFV0bXBra2FuQ1dUWVMYWoyRUJS2dBOUZ4NExhaERBNVcyWkpVTk9YcHBjT1lFK2xvUW5rbFdjYzAwekdONHhMU1hMbFBoWFV0bXBra2FuQ1dzUWVMYWoyRUJoU3huRFhpZnVEyZE9WNGJtQUhMM2lSZ1J0WXVzWldKaUROeThadTVONVVNUlJ3N3NFVFJZM2w_.pdf”
\n","event":[{"listen":"prerequest","script":{"type":"text/javascript","exec":[""],"id":"1a9316b9-3d11-41ab-a8c2-7196fb0d71e4"}},{"listen":"test","script":{"type":"text/javascript","exec":[""],"id":"f072137c-755e-410d-bcfa-a160b0215f8d"}}],"_postman_id":"c3185149-fd4d-4156-8e98-839fb2c33bfa"},{"name":"Testing (RapidLEI pre-release testing)","item":[{"name":"General - API Health Check","id":"a9bb0277-87bd-4477-9c19-530f31609c81","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"GET","header":[],"url":"https://apitesting.rapidlei.com/v1/health","description":"The health endpoint is used to determine the current version of the RapidLEI API service e.g.
\n{\n\"version\": \"3.7.12\"\n}\n\nThe Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. The OAuth2 specification (RFC 6749) requires this content type for token requests. Any other content-type will break OAuth2 compliant clients compatibility.
\n","key":"Content-Type","name":"Content-Type","type":"text","value":"application/x-www-form-urlencoded"},{"description":"The Accept request-header field can be used to specify certain media types which are acceptable for the response. The Accept request HTTP header advertises which content types, expressed as MIME types, the client is able to understand.
\n","key":"Accept","type":"text","value":"application/json"}],"body":{"mode":"urlencoded","urlencoded":[{"key":"grant_type","value":"client_credentials","description":"The grant_type parameter must be set to client_credentials
\n","type":"text"},{"key":"client_id","value":"reseller.email@test.com","description":"The client_id parameter must be set to reseller email address
\n","type":"text"},{"key":"client_secret","value":"xxxxxxAPI_key_from_My_Settingsxxxxxx","description":"The client_secret parameter must be set to API key
\n","type":"text"}]},"url":"https://apitesting.rapidlei.com/v1/auth/token","description":"This call requires an API Key from the 'My Settings' section of your account and the email address of the account. It delivers a Bearer Access Token to authenticate subsequent requests and a time to expiry in seconds. Within the Staging Environment the bearer token lasts for 3000 seconds (Allowing for manual use within a Postman collection), but within production this is limited to 900 seconds.
\n","urlObject":{"protocol":"https","path":["v1","auth","token"],"host":["apitesting","rapidlei","com"],"query":[],"variable":[]}},"response":[{"id":"d85d2282-5d24-493b-83fb-f6a45073376b","name":"Successful Response – access_token, token_type, expires_in parameters returned","originalRequest":{"method":"POST","header":[{"key":"Content-Type","name":"Content-Type","value":"application/x-www-form-urlencoded","type":"text"},{"key":"Accept","value":"application/json","type":"text"}],"body":{"mode":"urlencoded","urlencoded":[{"key":"grant_type","value":"client_credentials","description":"The grant_type parameter must be set to client_credentials","type":"text"},{"key":"client_id","value":"reseller.email@test.com","description":"The client_id parameter must be set to reseller email address","type":"text"},{"key":"client_secret","value":"123456789ABCDEF","description":"The client_secret parameter must be set to API key","type":"text"}]},"url":"https://apitesting.rapidlei.com/v1/auth/token"},"status":"OK","code":200,"_postman_previewlanguage":"json","header":[{"key":"Content-Type","value":"application/json","description":"","type":"text"},{"key":"Cache-Control","value":"no-store","description":"","type":"text"},{"key":"Pragma","value":"no-cache","description":"","type":"text"}],"cookie":[],"responseTime":null,"body":"{\n \"access_token\": \"MTQ0NjJkZmQ5OTM2NDE1ZTZjNGZmZjI3\",\n \"token_type\": \"bearer\",\n \"expires_in\": 30000\n}"},{"id":"5a126d95-6688-4bb0-8f33-bde1e1716c1a","name":"Unsuccessful Request – Client Authentication Failed","originalRequest":{"method":"POST","header":[{"key":"Content-Type","name":"Content-Type","value":"application/x-www-form-urlencoded","type":"text"},{"key":"Accept","value":"application/json","type":"text"}],"url":"https://apitesting.rapidlei.com/v1/auth/token"},"status":"Unauthorized","code":401,"_postman_previewlanguage":"json","header":[{"key":"Content-Type","value":"application/json","description":"","type":"text"},{"key":"Cache-Control","value":"no-store","description":"","type":"text"},{"key":"Pragma","value":"no-cache","description":"","type":"text"}],"cookie":[],"responseTime":null,"body":"{\r\n \"orderStatus\": \"authorization_error\",\r\n \"message\": \" Client Authentication failed due to either an invalid client_id (email address) or client_secret (API key from My Settings)\",\r\n \"errorUri\": \"https://rapidlei.com/api\"\r\n}"},{"id":"00d4497d-154f-49ca-89ab-003cb6afe58a","name":"Unsuccessful Request – Missing Request Parameter","originalRequest":{"method":"POST","header":[{"key":"Content-Type","name":"Content-Type","value":"application/x-www-form-urlencoded","type":"text"},{"key":"Accept","value":"application/json","type":"text"}],"body":{"mode":"urlencoded","urlencoded":[{"key":"grant_type","value":"client_credentials","description":"The grant_type parameter must be set to client_credentials","type":"text"},{"key":"client_id","value":"reseller.email@test.com","description":"The client_id parameter must be set to reseller email address","type":"text"}]},"url":"https://apitesting.rapidlei.com/v1/auth/token"},"status":"Bad Request","code":400,"_postman_previewlanguage":"json","header":[{"key":"Content-Type","value":"application/json","description":"","type":"text"},{"key":"Cache-Control","value":"no-store","description":"","type":"text"},{"key":"Pragma","value":"no-cache","description":"","type":"text"}],"cookie":[],"responseTime":null,"body":"{\r\n \"orderStatus\": \"invalid_request\",\r\n \"message\": \"Request is missing the 'client_secret' parameter\",\r\n\t\"errorUri\": \"https://rapidlei.com/api\"\r\n}"},{"id":"74945f60-5c9d-4503-b141-eae244d9f980","name":"Unsuccessful Request – Internal Server Error or Exception","originalRequest":{"method":"POST","header":[{"key":"Content-Type","name":"Content-Type","value":"application/x-www-form-urlencoded","type":"text"},{"key":"Accept","value":"application/json","type":"text"}],"body":{"mode":"urlencoded","urlencoded":[{"key":"grant_type","value":"client_credentials","description":"The grant_type parameter must be set to client_credentials","type":"text"},{"key":"client_id","value":"reseller.email@test.com","description":"The client_id parameter must be set to reseller email address","type":"text"},{"key":"client_secret","value":"123456789ABCDEF","description":"The client_secret parameter must be set to API key","type":"text"}]},"url":"https://apitesting.rapidlei.com/v1/auth/token"},"status":"Internal Server Error","code":500,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\r\n \"orderStatus\": \"server_error\",\r\n \"message\": \"Internal server error - If this problem persists, please contact the support team\",\r\n \"errorUri\": \"https://rapidlei.com/api\"\r\n}"},{"id":"5c562578-d116-4e2c-b37c-970da5a4d2dd","name":"Unsuccessful Request – Unsupported or Missing Grant Type","originalRequest":{"method":"POST","header":[{"key":"Content-Type","name":"Content-Type","value":"application/x-www-form-urlencoded","type":"text"},{"key":"Accept","value":"application/json","type":"text"}],"body":{"mode":"urlencoded","urlencoded":[{"key":"grant_type","value":"password","description":"The grant_type parameter must be set to client_credentials","type":"text"},{"key":"client_id","value":"reseller.email@test.com","description":"The client_id parameter must be set to reseller email address","type":"text"},{"key":"client_secret","value":"123456789ABCDEF","description":"The client_secret parameter must be set to API key","type":"text"}]},"url":"https://apitesting.rapidlei.com/v1/auth/token"},"status":"Bad Request","code":400,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\r\n \"orderStatus\": \"unsupported_grant_type\"\r\n}"}],"_postman_id":"87270023-4282-475b-b239-43cf8c7e90a0"},{"name":"Accounts - User Information","id":"17f869ed-b5eb-4a93-b65d-5a1ce99741ce","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"GET","header":[{"key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"key":"Content-Type","type":"text","value":"application/json"}],"url":"https://apitesting.rapidlei.com/v1/accounts/userinfo","description":"The userinfo endpoint is a secured API that returns basic information about the authenticated user.
\n","urlObject":{"protocol":"https","path":["v1","accounts","userinfo"],"host":["apitesting","rapidlei","com"],"query":[],"variable":[]}},"response":[],"_postman_id":"17f869ed-b5eb-4a93-b65d-5a1ce99741ce"},{"name":"Accounts - Create User","id":"9bf53568-3681-4c2c-9cd0-35a1a6373fc9","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.
\n","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity.
\n","key":"Content-Type","type":"text","value":"application/json"}],"body":{"mode":"raw","raw":"{\r\n \"firstName\": \"Peter\",\r\n \"lastName\": \"Anderson\",\r\n \"email\": \"useremail@server.com\",\r\n \"leiNumber\": \"984500B12AE2CF0PF040\"\r\n}"},"url":"https://apitesting.rapidlei.com/v1/accounts/users","description":"This endpoint adds a new user to the RapidLEI platform. A bearer access token from 'Authentication - Request Access Token' is required to submit the request. The new user's account will be linked to the Partners' LEI provided in the call. All users added to the platform will need to complete the registration process and agree to terms before being added. An email based challenge/response to the email address provided in the call verifies permission and email accuracy. If the challenge is not completed within 6 days, the entry will be deleted from the system (GDPR Privacy by Design). A web based system is available too. See 'Referral Link' details on https://rapidlei.com/partners/partner-resources/
\nPlease note that the Staging System does not have any ability to send emails other than to a default catchall of testing(a)rapidlei.com, so please discuss with the support team support(a)rapidlei.com to be able to test this function.
\nFinally, please note that you may be enabled to use this API call, but not the 'Full' LEI API. Please discuss with the support team support(a)rapidlei.com
\n","urlObject":{"protocol":"https","path":["v1","accounts","users"],"host":["apitesting","rapidlei","com"],"query":[],"variable":[]}},"response":[{"id":"2a95a397-b3b8-4160-98b6-4de05aa34c8d","name":"Successful Response – User Created","originalRequest":{"method":"POST","header":[{"key":"Authorization","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx","description":"he Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","type":"text"},{"key":"Content-Type","value":"application/json","description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","type":"text"}],"body":{"mode":"raw","raw":"{\r\n \"firstName\": \"Peter\",\r\n \"lastName\": \"Anderson\",\r\n \"email\": \"useremail@server.com\",\r\n \"leiNumber\": \"984500B12AE2CF0PF040\",\r\n \"organizationName\": \"Legal Entity Name Limited\"\r\n}","options":{"raw":{"language":"json"}}},"url":"https://apitesting.rapidlei.com/v1/accounts/users"},"status":"OK","code":200,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"message\": \"User created successfully.\"\n}"},{"id":"3715f387-0095-4f5a-bd9e-efb8a9b3cdce","name":"Unsuccessful Response – Referrer LEI is not found or not managed by RapidLEI","originalRequest":{"method":"POST","header":[{"key":"Authorization","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx","description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","type":"text"},{"key":"Content-Type","value":"application/json","description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","type":"text"}],"body":{"mode":"raw","raw":"{\r\n \"firstName\": \"Peter\",\r\n \"lastName\": \"Anderson\",\r\n \"email\": \"useremail@server.com\",\r\n \"leiNumber\": \"123400B12AE2CF0PF040\",\r\n \"organizationName\": \"Legal Entity Name Limited\"\r\n}","options":{"raw":{"language":"json"}}},"url":"https://apitesting.rapidlei.com/v1/accounts/users"},"status":"Internal Server Error","code":500,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderStatus\": \"server_error\",\n \"message\": \"The 'leiNumber' parameter needs to be an LEI managed by RapidLEI and linked with your account. Please contact our support team to discuss options.\",\n \"errorUri\": \"https://rapidlei.com/api\"\n}"},{"id":"b70c8783-83df-47f6-8a8a-a592efa983dd","name":"Unsuccessful Response – Parameter Missing","originalRequest":{"method":"POST","header":[{"key":"Authorization","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx","description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","type":"text"},{"key":"Content-Type","value":"application/json","description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","type":"text"}],"body":{"mode":"raw","raw":"{\r\n \"lastName\": \"Anderson\",\r\n \"email\": \"useremail@server.com\",\r\n \"leiNumber\": \"984500B12AE2CF0PF040\",\r\n \"organizationName\": \"Legal Entity Name Limited\"\r\n}","options":{"raw":{"language":"json"}}},"url":"https://apitesting.rapidlei.com/v1/accounts/users"},"status":"Bad Request","code":400,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderStatus\": \"invalid_request\",\n \"message\": \"Request is missing the 'firstName' parameter\",\n \"errorUri\": \"https://rapidlei.com/api\"\n}"},{"id":"01c8b2db-4469-40cf-8900-bccb3b64d22e","name":"Unsuccessful Response – Invalid Email Address","originalRequest":{"method":"POST","header":[{"key":"Authorization","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx","description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","type":"text"},{"key":"Content-Type","value":"application/json","description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","type":"text"}],"body":{"mode":"raw","raw":"{\r\n \"firstName\": \"Peter\",\r\n \"lastName\": \"Anderson\",\r\n \"email\": \"useremailserver.com\",\r\n \"leiNumber\": \"984500B12AE2CF0PF040\",\r\n \"organizationName\": \"Legal Entity Name Limited\"\r\n}","options":{"raw":{"language":"json"}}},"url":"https://apitesting.rapidlei.com/v1/accounts/users"},"status":"Bad Request","code":400,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{ \r\n \"orderStatus\": \"invalid_request\", \r\n \"message\": \"Please provide a valid email address format user@domain.com or first.last@domain.co.uk etc\", \r\n \"errorUri\": \"https://rapidlei.com/api\" \r\n}"},{"id":"a07e784e-43a3-4553-9e86-6a79869eb810","name":"Unsuccessful Response – Invalid LEI Format","originalRequest":{"method":"POST","header":[{"key":"Authorization","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx","description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","type":"text"},{"key":"Content-Type","value":"application/json","description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","type":"text"}],"body":{"mode":"raw","raw":"{\r\n \"firstName\": \"Peter\",\r\n \"lastName\": \"Anderson\",\r\n \"email\": \"useremail@server.com\",\r\n \"leiNumber\": \"984500B12AE2CF0PF0\",\r\n \"organizationName\": \"Legal Entity Name Limited\"\r\n}","options":{"raw":{"language":"json"}}},"url":"https://apitesting.rapidlei.com/v1/accounts/users"},"status":"Bad Request","code":400,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderStatus\": \"invalid_request\",\n \"message\": \"Please ensure the 'leiNumber' is a valid ISO 17442 format LEI (20 characters).\",\n \"errorUri\": \"https://rapidlei.com/api\"\n}"},{"id":"a1e4faec-02b6-4b35-86d3-e18cb9ce45b6","name":"Unsuccessful Response – Request to add user failed as the user already exists","originalRequest":{"method":"POST","header":[{"key":"Authorization","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx","description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","type":"text"},{"key":"Content-Type","value":"application/json","description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","type":"text"}],"body":{"mode":"raw","raw":"{\r\n \"firstName\": \"Peter\",\r\n \"lastName\": \"Anderson\",\r\n \"email\": \"useremail@server.com\",\r\n \"lei\": \"984500B12AE2CF0PF040\",\r\n \"organizationName\": \"Legal Entity Name Limited\"\r\n}","options":{"raw":{"language":"json"}}},"url":"https://apitesting.rapidlei.com/v1/accounts/users"},"status":"Internal Server Error","code":500,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderStatus\": \"server_error\",\n \"message\": \"We already have a user account with the email address supplied. If in doubt please contact our support team.\",\n \"errorUri\": \"https://rapidlei.com/api\"\n}"},{"id":"02842032-1daa-4b62-a1bf-710f9496663e","name":"Unsuccessful Response – Referrer feature is not enabled","originalRequest":{"method":"POST","header":[{"key":"Authorization","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx","description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","type":"text"},{"key":"Content-Type","value":"application/json","description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","type":"text"}],"body":{"mode":"raw","raw":"{\r\n \"firstName\": \"Peter\",\r\n \"lastName\": \"Anderson\",\r\n \"email\": \"useremail@server.com\",\r\n \"leiNumber\": \"984500B12AE2CF0PF040\",\r\n \"organizationName\": \"Legal Entity Name Limited\"\r\n}","options":{"raw":{"language":"json"}}},"url":"https://apitesting.rapidlei.com/v1/accounts/users"},"status":"Internal Server Error","code":500,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderStatus\": \"server_error\",\n \"message\": \"Sorry, you are unable to add users. The Referrer feature has not been enabled for your account. If in doubt, please talk to our support team.\",\n \"errorUri\": \"https://rapidlei.com/api\"\n}"},{"id":"13c9ba01-36ec-4c54-b581-ad3b8c17afc6","name":"Unsuccessful Response – Parameter Length Error","originalRequest":{"method":"POST","header":[{"key":"Authorization","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx","description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","type":"text"},{"key":"Content-Type","value":"application/json","description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","type":"text"}],"body":{"mode":"raw","raw":"{\r\n \"firstName\": \"Peter middle name example is much bigger than we allow\",\r\n \"lastName\": \"Anderson\",\r\n \"email\": \"useremail@server.com\",\r\n \"leiNumber\": \"984500B12AE2CF0PF040\",\r\n \"organizationName\": \"Legal Entity Name Limited\"\r\n}","options":{"raw":{"language":"json"}}},"url":"https://apitesting.rapidlei.com/v1/accounts/users"},"status":"Bad Request","code":400,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderStatus\": \"invalid_request\",\n \"message\": \"Parameter 'firstName' should not be greater than 50 characters\",\n \"errorUri\": \"https://rapidlei.com/api\"\n}"},{"id":"315e96db-b9a3-4787-bd7e-00d4bcd5bde2","name":"Unsuccessful Response – Missing organizaionName","originalRequest":{"method":"POST","header":[{"key":"Authorization","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx","description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","type":"text"},{"key":"Content-Type","value":"application/json","description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","type":"text"}],"body":{"mode":"raw","raw":"{\r\n \"firstName\": \"Peter\",\r\n \"lastName\": \"Anderson\",\r\n \"email\": \"useremail@server.com\",\r\n \"leiNumber\": \"984500B12AE2CF0PF040\"\r\n}","options":{"raw":{"language":"json"}}},"url":"https://apitesting.rapidlei.com/v1/accounts/users"},"status":"Bad Request","code":400,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderStatus\": \"invalid_request\",\n \"message\": \"Request is missing the 'organizaionName' parameter\",\n \"errorUri\": \"https://rapidlei.com/api\"\n}"}],"_postman_id":"9bf53568-3681-4c2c-9cd0-35a1a6373fc9"},{"name":"LEI – Query Supported Jurisdictions","id":"8f4537e3-e581-4809-a771-9bd40ee5d9e6","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"GET","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.
\n","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity.
\n","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://apitesting.rapidlei.com/v1/jurisdictions","description":"This API call is used to query supported jurisdictions and confidence levels. Confidence level 10 is fully automated including Authorised Representative verification resulting in rapid, efficient LEI issuance. Confidence level 0 is a manually processed jurisdiction requiring manual verification of data on the business registry. Confidence levels 1-9 indicate the expected confidence level in gathering data from the registry. 9 indicates all LE-RD Level 1 data is usually available. 8 indicates most LE-RD Level 1 data is usually available. For additional details on how best to use this function please contact the RapidLEI support team.
\n","urlObject":{"protocol":"https","path":["v1","jurisdictions"],"host":["apitesting","rapidlei","com"],"query":[],"variable":[]}},"response":[{"id":"24f3e46a-e200-4d17-bab8-c8de6ecf489f","name":"Successful Response – List of Jurisdictions returned","originalRequest":{"method":"GET","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://apitesting.rapidlei.com/v1/jurisdictions"},"status":"OK","code":200,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"countries\": [\n {\n \"jurisdiction\": \"DK\",\n \"confidenceLevel\": \"10\"\n },\n {\n \"jurisdiction\": \"HK\",\n \"confidenceLevel\": \"0\"\n },\n {\n \"jurisdiction\": \"NL\",\n \"confidenceLevel\": \"7\"\n }\n ],\n \"states\": [\n\t {\n\t \"jurisdiction\": \"US-KS\",\n\t \"confidenceLevel\": \"10\"\n\t },\n\t {\n\t \"jurisdiction\": \"US-NJ\",\n\t \"confidenceLevel\": \"6\"\n\t },\n\t {\n\t \"jurisdiction\": \"US-DC\",\n\t \"confidenceLevel\": \"0\"\n\t }\n ]\n}"},{"id":"ede98c1d-3418-48cc-87f3-64c4b090b9fb","name":"Unsuccessful Response - User not allowed to use the Full API, only the ‘Create User’ endpoint","originalRequest":{"method":"GET","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://apitesting.rapidlei.com/v1/jurisdictions"},"status":"Unauthorized","code":401,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderStatus\": \"authorization_error\",\n \"message\": \"You do not have the ability to use the Full RapidLEI API from this account – you are configured only to use the ‘Create User’ endpoint, please contact our support team on support@rapidlei.com\",\n \"errorUri\": \"https://rapidlei.com/api\"\n}"},{"id":"b408ec5d-6f30-47bd-bbe4-7fdc1671611d","name":"Unsuccessful Response - Unknown Error or Exception during processing request","originalRequest":{"method":"GET","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://apitesting.rapidlei.com/v1/jurisdictions"},"status":"Internal Server Error","code":500,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderStatus\": \"server_error\",\n \"message\": \"We've been unable to process your request - please contact our support team.\",\n \"errorUri\": \"https://rapidlei.com/api\"\n}"}],"_postman_id":"8f4537e3-e581-4809-a771-9bd40ee5d9e6"},{"name":"LEI – Pre-Submission Entity Search","id":"a5778775-ae82-4427-9b49-dc03a599c1f5","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.
\n","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity.
\n","key":"Content-Type","name":"Content-Type","type":"text","value":"application/json"}],"body":{"mode":"raw","raw":"{\r\n \"keyword\": \"Ubisecure Holdings\",\r\n \"legalJurisdiction\": \"GB\",\r\n \"entityType\": \"GENERAL\"\r\n}","options":{"raw":{"language":"json"}}},"url":"https://apitesting.rapidlei.com/v1/leis/searchByKeyword","description":"The Pre-Submission Entity Search ensures data accuracy for New LEI or Import LEI requests by performing an initial search of the jurisdiction. Legal Name spelling, form and capitalization as well as Registration Authority Entity ID (Business Registry Number) accuracy are improved using this API endpoint. The API Endpoint returns one or more potential legal entities along with a 'searchId' and 'companyId' - Please see LEI – Create New LEI and LEI – Import Existing LEI for details.
\nIt is highly recommended to search by the Business Registry Number first as this is the most accurate method. The name of the Legal Entity may be too generic and may return too many results to display all, resulting in the entity not being found.
\nThe keyword helps identify the Legal Entity. It can be either:
\nName of the Legal Entity e.g. ABC Limited
\nCompany Number for the Legal Entity e.g. 68678678
\nThe LEI number to be imported/transferred. e.g. 89450051ZRDOL9KEWH63
\nlegalJurisdiction
\nA supported legal jurisdiction is required. e.g. DK or US-CA for California in the United States
\nPlease note that the following entityType's are NOT supported within the pre-submission search:-
\nThe Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.
\n","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity.
\n","key":"Content-Type","name":"Content-Type","type":"text","value":"application/json"}],"body":{"mode":"raw","raw":"{\n \"companyName\": \"ABC Limited\",\n \"companyNumber\": \"68678678\",\n \"searchId\": \"9cf0521c2dfc4502bfa3f7bb49daca77\",\n \"companyId\": \"8ba68d90a7324ba2bbbbe87bc227c461\",\n \"legalJurisdiction\": \"DK\",\n \"firstName\": \"Peter\",\n \"lastName\": \"Anderson\",\n \"isLevel2DataAvailable\": false,\n \"reportingExceptionReason\": \"NATURAL_PERSONS\",\n \"multiYearSupport\": 3,\n \"entityType\": \"GENERAL\",\n \"userComments\": \"optional comments\",\n \"notificationUrl\": \"https://www.someotherserver.com/notify/me/when/lei/is/ready\",\n \"notificationToken\": \"Sq31YkqGWKXGEpeJGZwM\",\n \"loaFile\": {\n \"fileName\": \"My Letter of Authorization.docx\",\n \"fileUrl\": \"http://www.example.com/LoA.docx?token=GFVHGSahG6HGjsggdgxxSecurity-Token-examplexxGFDsdd\"\n },\n \"corroboratingFiles\": [\n {\n \"fileName\": \"Corroborating Data 1.docx\",\n \"fileUrl\": \"http://www.example.com/file.docx\"\n },\n {\n \"fileName\": \" Corroborating Data 2.docx\",\n \"fileData\": \"data:application/octet–stream;base64, ldfhaklsjdfhkasjfjsdfgakjsfgakjsdagsdf...\"\n }\n ]\n}"},"url":"https://apitesting.rapidlei.com/v1/leis/orders/create","description":"This API endpoint initiates the workflow process to request a new LEI (i.e. An LEI will be created, so the call assumes that the Legal Entity does not already have an LEI, but it also tests that assumption and will provide an error if one is found - see the examples for more information). The bearer access Token from 'Authentication - Request Access Token' is required to submit the request along with the following mandatory / optional parameters.
\nPlease note GDPR (General Data Protection Regulations) when transferring personal data. Ensure permission of the Legal Entity.
\ncompanyName
Name of the Legal Entity noting that accuracy here helps the overall process flow and accuracy of any potential duplicate test. e.g. ABC Limited
companyNumber
Company Number, (Registration Authority Entity ID) for the Legal Entity noting that accuracy here helps the overall process flow and accuracy of any potential duplicate test. e.g. 068678678 - Tip - don't forget to ensure any leading '0's are maintained - this is common for UK based numbers. For Funds which sometimes do not have a Registration Authority Entity ID, you may leave this field empty ensuring entityType is set to FUND. There may be a legitimate edge case such as a Legal Entity in Germany, or South Carolina which does not have any number. In these rare cases please use entityType OTHER
legalJurisdiction
A supported legal jurisdiction is required. e.g. DK or US-CA for California in the United States
firstName
The First Name(s) of the Authorised Representative with the responsibility/authority to request and approve the creation of an LEI e.g. Peter
lastName
The Last Name of the Authorised Representative e.g. Anderson
isLevel2DataAvailable
A Boolean value - If the Legal Entity consolidates accounts with parental entities, then Level 2 data will be required. This data is not to be provided by API calls. Due to the complex nature of the data possibilities, the GUI interface of the RapidLEI Identity Platform must be used i.e. true if level 2 data is available and false if reporting exceptions are to be used.
multiYearSupport
An integer from 1 to 5. Please see https://rapidlei.com/lei-pricing/ for details. Please default to 1 as the standard option.
reportingExceptionReason
If isLevel2DataAvailable is set to false, then it indicates there is no level 2 information, so please highlight the appropriate reporting exception reason which will be used for BOTH Direct and Ultimate Parent reporting. If any other combination of reporting exceptions is required, please set isLevel2DataAvailable to true and use the GUI
NATURAL_PERSONS
\nNON_CONSOLIDATING
\nNO_KNOWN_PERSON
\nPrior to the release of LE-RR Version 2.1, the following reasons were specifically used for Level 2 scenarios where parental accounting was present, but LEI details were absent. The removal of PNI data by the ROC (Regulatory Oversight Committee) has deprecated these exception reasons. Please see this announcement for details (https://www.leiroc.org/publications/gls/roc_20220107.pdf)
\nDeprecated exception reasons:-
\nCONSENT_NOT_OBTAINED
\nLEGAL_OBSTACLES
\nBINDING_LEGAL_COMMITMENTS
\nDETRIMENT_NOT_EXCLUDED
\nDISCLOSURE_DETRIMENTAL
\nHave been replaced by a single reporting exception configured within the GUI along with other level 2 parental reporting and Fund reporting options:-
\nsearchId & companyId
When the LEI – Pre-Submission Entity Search function is used prior to a New LEI being created, submission of the 'searchId' and 'companyId' together with the EXACT Name of the companyName, legalJurisdiction and companyNumber will accelerate the speed at which the LEI is issued.
entityType
If entityType is not included, we'll assume the request is for a legal entity. A positive indication of the entityType will increase the efficiency of the RapidLEI vetting team and any associated workflows.
GENERAL
\nSOLE_PROPRIETOR
\nFUND
\nWILL_PENSION
\nTRUST
\nOTHER
\nNotes:- If Submitting a FUND it is advisable to include the fund deed as 'Evidence of Authority' in the corroboratingFiles as this will avoid the need to ask for this document.
\nnotificationUrl
To avoid unnecessary polling, webhooks can be used to pass orderStatus information in real time. A webhook is a user-defined HTTP (ideally HTTPS) endpoints which can accept POST requests for real time synchronous LEI processing. An optional security token may be used to avoid replay attacks, however the notificationUrl may also contain additional URL parameters. Webhook ApS in Denmark, ran by Simon Fredsted, offers a very simple listening service for testing webhooks. Please see https://webhook.site/ for details and usage guidelines. The two parameters returned in the RequestBody are - orderTrackingCode and orderStatus, with the optional security token being returned as notificationTokene.g. https://www.someotherserver.com/notify/me/when/lei/is/ready
or https://www.someotherserver.com/notify/me/when/lei/is/ready?type=exampletype&token=URL_based_token_examplePLEASE NOTE - Redirects are not guaranteed to be supported in all cases therefore please ensure the correct URL and any final / characters in the URL are sent.
notificationToken
An optional unique token to avoid the possibility of a third party accidentally making a call to a static notification URL and therefore maliciously affecting the workflow.
e.g. Sq31YkqGWKXGEpeJGZwM\"
userComments
An optional comment or instruction to aid efficient processing of the LEI by the RapidLEI vetting team – to be used primarily for simple comments < 1000 characters to avoid the need to send additional corroborating documents.
corroboratingFiles Up to 5 additional files which may aid vetting or validation of the Application. Please note the upload limit of 20MB each.
\nnextRenewalDate
nextRenewalDate is an advanced customization option which requires multi-year support and is applicable to enterprises who require alignment of LEI issuance/renewal around specific dates. Please discuss in detail before implementing this function. nextRenewalDate is a date in the future which indicates the 'nextRenewalDate' of the LEI. If omitted, the date will be set to one calendar year from initial issuance of the LEI.
is3rdPartyRequest
If is3rdPartyRequest is set to true an LoA MUST be uploaded which highlights the agreement between the 3rd Party and the Legal Entity. For more details please discuss with our legal team legal(a)rapidlei.com. Please discuss in detail before implementing this function
The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.
\n","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity.
\n","key":"Content-Type","type":"text","value":"application/json"}],"body":{"mode":"raw","raw":"{\n \"companyName\": \"ABC Limited\",\n \"companyNumber\": \"68678678\",\n \"leiNumber\": \"213800855GFRCT277149\",\n \"legalJurisdiction\": \"DK\",\n \"firstName\": \"Peter\",\n \"lastName\": \"Anderson\",\n \"email\": \"peter.anderson@testmail.com\",\n \"phone\": \"003489348573945\",\n \"isLevel2DataAvailable\": false,\n \"reportingExceptionReason\": \"NATURAL_PERSONS\",\n \"multiYearSupport\": 3,\n \"userComments\": \"optional comments\",\n \"notificationUrl\": \"https://www.someotherserver.com/notify/me/when/lei/is/ready\",\n \"notificationToken\": \"Sq31YkqGWKXGEpeJGZwM\",\n \"mergedOrRetiredLeiComments\": \"Optional comments to mention the reasons to import MERGED or RETIRED LEI\",\n \"loaFile\": {\n \"fileName\": \"My Letter of Authorization.docx\",\n \"fileUrl\": \"http://www.example.com/LoA.docx?token=GFVHGSahG6HGjsggdgxxSecurity-Token-examplexxGFDsdd\"\n },\n \"corroboratingFiles\": [\n {\n \"fileName\": \"Corroborating Data 1.docx\",\n \"fileUrl\": \"http://www.example.com/file.docx\"\n },\n {\n \"fileName\": \" Corroborating Data 2.docx\",\n \"fileData\": \"data:application/octet–stream;base64, ldfhaklsjdfhkasjfjsdfgakjsfgakjsdagsdf...\"\n }\n ]\n}"},"url":"https://apitesting.rapidlei.com/v1/leis/orders/import","description":"This API endpoint initiates the workflow process to transfer an existing LEI (i.e. An LEI must already exist and have a GLEIF Status of ISSUED, LAPSED or rarely RETIRED). The bearer access Token from 'Authentication - Request Access Token' is required to submit the request along with the following mandatory / optional parameters.
\nPlease note GDPR (General Data Protection Regulations) when transferring personal data. Ensure permission of the Legal Entity.
\ncompanyName
Name of the Legal Entity noting that accuracy here helps the overall process flow and accuracy of any potential duplicate test. e.g. ABC Limited
companyNumber
Company Number, (Registration Authority Entity ID) for the Legal Entity noting that accuracy here helps the overall process flow and accuracy of any potential duplicate test. e.g. 068678678 - Tip - don't forget to ensure any leading '0's are maintained - this is common for UK based numbers. For Funds which sometimes do not have a Registration Authority Entity ID, you may leave this field empty ensuring entityType is set to FUND. There may be a legitimate edge case such as a Legal Entity in Germany, or South Carolina which does not have any number. In these rare cases please use entityType OTHER
legalJurisdiction
A supported legal jurisdiction is required. e.g. DK or US-CA for California in the United States
leiNumber
The LEI number to be imported/transferred.
e.g. 89450051ZRDOL9KEWH63
firstName
The First Name(s) of the Authorised Representative with the responsibility/authority to request and approve the creation of an LEI e.g. Peter
lastName
The Last Name of the Authorised Representative e.g. Anderson
email
The email of the contact person who is authorized to request the transfer of the LEI e.g. peter.anderson@testmail.com (Please note that this is a requirement of the GLEIF LEI Transfer Protocol and must be transferred as part of the initial call. This differs from the creation of an LEI where this information is not usually taken – please ensure permission of the Legal Entity to allow the transfer of this personal data)
phone
The phone number of the contact person who is authorized to request the transfer of the LEI e.g. 003489348573945 (Please note that this is a requirement of the GLEIF LEI Transfer Protocol and must be transferred as part of the initial call. This differs from the creation of an LEI where this information is not usually taken – please ensure permission of the Legal Entity to allow the transfer of this personal data)
isLevel2DataAvailable
A Boolean value - If the Legal Entity consolidates accounts with parental entities, then Level 2 data will be required. This data is not to be provided by API calls. Due to the complex nature of the data possibilities, the GUI interface of the RapidLEI Identity Platform must be used i.e. true if level 2 data is available and false if reporting exceptions are to be used.
multiYearSupport
An integer from 1 to 5. Please see https://rapidlei.com/lei-pricing/ for details. Please default to 1 as the standard option.
reportingExceptionReason
If isLevel2DataAvailable is set to false, then it indicates there is no level 2 information, so please highlight the appropriate reporting exception reason which will be used for BOTH Direct and Ultimate Parent reporting. If any other combination of reporting exceptions is required, please set isLevel2DataAvailable to true and use the GUI
NATURAL_PERSONS
\nNON_CONSOLIDATING
\nNO_KNOWN_PERSON
\nPrior to the release of LE-RR Version 2.1, the following reasons were specifically used for Level 2 scenarios where parental accounting was present, but LEI details were absent. The removal of PNI data by the ROC (Regulatory Oversight Committee) has deprecated these exception reasons. Please see this announcement for details (https://www.leiroc.org/publications/gls/roc_20220107.pdf)
\nDeprecated exception reasons:-
\nCONSENT_NOT_OBTAINED
\nLEGAL_OBSTACLES
\nBINDING_LEGAL_COMMITMENTS
\nDETRIMENT_NOT_EXCLUDED
\nDISCLOSURE_DETRIMENTAL
\nHave been replaced by a single reporting exception configured within the GUI along with other level 2 parental reporting and Fund reporting options:-
\nentityType
If entityType is not included, we'll assume the request is for a legal entity. A positive indication of the entityType will increase the efficiency of the RapidLEI vetting team and any associated workflows.
GENERAL
\nSOLE_PROPRIETOR
\nFUND
\nWILL_PENSION
\nTRUST
\nOTHER
\nNotes:- If Submitting a FUND it is advisable to include the fund deed as 'Evidence of Authority' in the corroboratingFiles as this will avoid the need to ask for this document.
\nnotificationUrl
To avoid unnecessary polling, webhooks can be used to pass orderStatus information in real time. A webhook is a user-defined HTTP (ideally HTTPS) endpoints which can accept POST requests for real time synchronous LEI processing. An optional security token may be used to avoid replay attacks, however the notificationUrl may also contain additional URL parameters. Webhook ApS in Denmark, ran by Simon Fredsted, offers a very simple listening service for testing webhooks. Please see https://webhook.site/ for details and usage guidelines. The two parameters returned in the RequestBody are - orderTrackingCode and orderStatus, with the optional security token being returned as notificationTokene.g. https://www.someotherserver.com/notify/me/when/lei/is/ready
or https://www.someotherserver.com/notify/me/when/lei/is/ready?type=exampletype&token=URL_based_token_examplePLEASE NOTE - Redirects are not guaranteed to be supported in all cases therefore please ensure the correct URL and any final / characters in the URL are sent.
notificationToken
An optional unique token to avoid the possibility of a third party accidentally making a call to a static notification URL and therefore maliciously affecting the workflow.
e.g. Sq31YkqGWKXGEpeJGZwM\"
userComments
An optional comment or instruction to aid efficient processing of the LEI by the RapidLEI vetting team – to be used primarily for simple comments < 1000 characters to avoid the need to send additional corroborating documents.
corroboratingFiles Up to 5 additional files which may aid vetting or validation of the Application. Please note the upload limit of 20MB each.
\nnextRenewalDate
nextRenewalDate is an advanced customization option which requires multi-year support and is applicable to enterprises who require alignment of LEI issuance/renewal around specific dates. Please discuss in detail before implementing this function. nextRenewalDate is a date in the future which indicates the 'nextRenewalDate' of the LEI. If omitted, the date will be set to one calendar year from initial issuance of the LEI.
is3rdPartyRequest
If is3rdPartyRequest is set to true an LoA MUST be uploaded which highlights the agreement between the 3rd Party and the Legal Entity. For more details please discuss with our legal team legal(a)rapidlei.com. Please discuss in detail before implementing this function
The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.
\n","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity.
\n","key":"Content-Type","name":"Content-Type","type":"text","value":"application/json"}],"body":{"mode":"raw","raw":"{\n \"orderTrackingCode\": \"YEaadmjQbt00uY0mepcg\",\n \"loaFiles\": [\n {\n \"fileName\": \"LoA1. pdf\",\n \"fileData\": \"data:text/plain;base64,dGVzdA==\"\n },\n {\n \"fileName\": \"LoA2.pdf\",\n \"fileUrl\": \"https://www.lean.org/downloads/sampleboardreport.pdf\"\n }\n ], \n \"eoaFiles\": [\n {\n \"fileName\": \"EoaFile1.docx\",\n \"fileData\": \"data:text/plain;base64,dGVzdA==\"\n },\n {\n \"fileName\": \"EoaFile2.pdf\",\n \"fileUrl\": \"https://www.lean.org/downloads/sampleboardreport.pdf\"\n }\n ],\n \"corroboratingFiles\": [\n {\n \"fileName\": \"CorroboratingFile1.docx\",\n \"fileData\": \"data:text/plain;base64,dGVzdA==\"\n },\n {\n \"fileName\": \"CorroboratingFile2.pdf\",\n \"fileUrl\": \"https://www.lean.org/downloads/sampleboardreport.pdf\"\n }\n ]\n}"},"url":"https://apitesting.rapidlei.com/v1/leis/uploadFiles","description":"This API endpoint mimics the GUI facility to upload files at any time, for any LEI order with an associated ‘orderTrackingCode’. Files can be of type LoA (Letter of Authorization), EoA (Evidence of Authority) or other Corroborating Data. Orders submitted via GUI (Graphical User Interface) or via Bulk XLS methods, do not have unique API ‘orderTrackingCode’ and therefore files must be associated with these orders using the GUI interface only. The bearer access Token from 'Authentication - Request Access Token' is required to submit the request along with the following mandatory / optional parameters.
\n– orderTrackingCode
\nA unique token returned when any New, Import or Renew order is created. e.g. 987a9sd8f7a9sd8f7
\nloaFiles
A Letter of Authorization (LoA) is used to provide linkage between the Applicant applying for the LEI & a Valid Authorised Representative found on a Registry for the Legal Entity. The Applicant applying for the LEI will be the Authorised Representative name submitted as firstName lastName parameters. The Letter of Authorization (LoA) will be a document from one of the Valid Authorised Authorised Representatives, this document will state that the valid signer is empowering the Applicant of the LEI (Authorised Representative Name already given) to manage the LEI on their behalf. Please note that if a valid Authorised Representative wishes to manage the LEI themselves directly then the Authorised Representative Name provided in the order creation can be amended in the GUI.
eoaFiles
Evidence of Authority (EoA) is used to provide additional clarification/evidence of the empowered Authorised Representative name submitted as firstName lastName parameters. A typical common example would be Articles of Association for an LLC in Delaware in the United States which does not maintain records of empowered individuals within their registry. For more details, please discuss with our legal team legal(a)rapidlei.com. Multiple EoA's may be submitted using either the fileData method or fileUrl method. Up to 10 additional files may be uploaded.
corroboratingFiles
Up to 10 additional files which may aid vetting or validation of the Application. Please note the upload limit of 20MB each.
The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.
\n","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity.
\n","key":"Content-Type","name":"Content-Type","type":"text","value":"application/json"}],"body":{"mode":"raw","raw":"{\n \"orderTrackingCode\": \"987a9sd8f7a9sd8f7\",\n \"userComments\": \"Page 10 of the annual report details the level 2 parental structure your vetting team needs\"\n}"},"url":"https://apitesting.rapidlei.com/v1/leis/uploadComments","description":"This API endpoint mimics the GUI facility to upload comments at any time, for any LEI order with an associated ‘orderTrackingCode’. Comments help provide our vetting team with essential details to help process LEI applications more efficiently
\n– orderTrackingCode
\nA unique token returned when any New, Import or Renew order is created. e.g. 987a9sd8f7a9sd8f7
\n– userComments
\nA comment or instruction to aid efficient processing of the LEI by the RapidLEI vetting team – to be used primarily for simple comments < 1000 characters to avoid the need to send additional corroborating documents.
\n","urlObject":{"protocol":"https","path":["v1","leis","uploadComments"],"host":["apitesting","rapidlei","com"],"query":[],"variable":[]}},"response":[{"id":"9c069523-d09c-45d8-aeaf-00c22e8d3ee8","name":"Successful Response – Comments Submitted Successfully","originalRequest":{"method":"POST","header":[{"key":"Authorization","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx","description":"A Bearer Token must be set to a valid access token in the Authorization header","type":"text"},{"key":"Content-Type","name":"Content-Type","value":"application/json","description":"The Accept header is used by HTTP clients to tell the server what content types they'll accept.","type":"text"}],"body":{"mode":"raw","raw":"{\r\n \"orderTrackingCode\": \"987a9sd8f7a9sd8f7\",\r\n \"userComments\": \"Page 10 of the annual report details the level 2 parental structure your vetting team needs\"\r\n}","options":{"raw":{"language":"json"}}},"url":"https://apitesting.rapidlei.com/v1/leis/uploadComments"},"status":"OK","code":200,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderTrackingCode\": \"987a9sd8f7a9sd8f7\",\n \"message\": \"userComments successfully submitted\"\n}"},{"id":"d8d7f9b6-2153-420e-a1c1-815520fd890e","name":"Unsuccessful Response – All Parameters or entire JSON body missing Copy","originalRequest":{"method":"POST","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"key":"Content-Type","name":"Content-Type","value":"application/json","description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","type":"text"}],"body":{"mode":"raw","raw":"{}","options":{"raw":{"language":"json"}}},"url":"https://apitesting.rapidlei.com/v1/leis/uploadComments"},"status":"Bad Request","code":400,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\r\n \"orderStatus\": \"invalid_request\",\r\n \"message\": \"The request is missing mandatory parameters. Please check our API documentation available at https://rapidlei.com/developers\",\r\n \"errorUri\": \"https://rapidlei.com/api\"\r\n}"},{"id":"3237f151-58ab-4f79-b7f2-c38bde4b0abf","name":"Unsuccessful Response – 'orderTrackingCode' Parameter Missing","originalRequest":{"method":"POST","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"key":"Content-Type","name":"Content-Type","value":"application/json","description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","type":"text"}],"body":{"mode":"raw","raw":"{\r\n \"userComments\": \"Page 10 of the annual report details the level 2 parental structure your vetting team needs\"\r\n}","options":{"raw":{"language":"json"}}},"url":"https://apitesting.rapidlei.com/v1/leis/uploadComments"},"status":"Bad Request","code":400,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\r\n \"orderStatus\": \"invalid_request\",\r\n \"message\": \"Request is missing the 'orderTrackingCode' parameter\",\r\n \"errorUri\": \"https://rapidlei.com/api\"\r\n}"},{"id":"2bcb3650-a988-4c36-bdcd-b17057901041","name":"Unsuccessful Response – 'userComments' Parameter Missing Copy","originalRequest":{"method":"POST","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"key":"Content-Type","name":"Content-Type","value":"application/json","description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","type":"text"}],"body":{"mode":"raw","raw":"{\r\n \"orderTrackingCode\": \"987a9sd8f7a9sd8f7\"\r\n}","options":{"raw":{"language":"json"}}},"url":"https://apitesting.rapidlei.com/v1/leis/uploadComments"},"status":"Bad Request","code":400,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\r\n \"orderStatus\": \"invalid_request\",\r\n \"message\": \"Request is missing the 'userComments' parameter\",\r\n \"errorUri\": \"https://rapidlei.com/api\"\r\n}"},{"id":"fe0cc89a-0e1d-489d-b59e-32287be8f229","name":"Unsuccessful Response – Maximum character limit exceeded","originalRequest":{"method":"POST","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"key":"Content-Type","name":"Content-Type","value":"application/json","description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","type":"text"}],"body":{"mode":"raw","raw":"{\r\n \"orderTrackingCode\": \"987a9sd8f7a9sd8f7\",\r\n \"userComments\": \"Well, we seem to have made the comment length too much for the API endpoint to swallow, so we need to reduce this down to less than 2000 characters. Here’s some padding to highlight what 2001 characters looks like 78901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901 makes 2001\"\r\n}","options":{"raw":{"language":"json"}}},"url":"https://apitesting.rapidlei.com/v1/leis/uploadComments"},"status":"Bad Request","code":400,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\r\n \"orderStatus\": \"invalid_request\",\r\n \"message\": \"Parameter 'userComments' should not be greater than 2000 characters.\",\r\n \"errorUri\": \"https://rapidlei.com/api\"}\r\n"},{"id":"5e47251e-b486-46d6-9a17-8b34a3e97076","name":"Unsuccessful Response – invalid 'orderTrackingCode'","originalRequest":{"method":"POST","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"key":"Content-Type","name":"Content-Type","value":"application/json","description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","type":"text"}],"body":{"mode":"raw","raw":"{\r\n \"orderTrackingCode\": \"Mycode\",\r\n \"userComments\": \"Page 10 of the annual report details the level 2 parental structure your vetting team needs\"\r\n}","options":{"raw":{"language":"json"}}},"url":"https://apitesting.rapidlei.com/v1/leis/uploadComments"},"status":"Bad Request","code":400,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\r\n \"orderStatus\": \"invalid_request\",\r\n \"message\": \" Invalid Tracking Code - please contact our support team quoting your order tracking code, which can be found in the GUI interface, by clicking on the ‘Enhanced Detail’ from the LEI list. \",\r\n \"errorUri\": \"https://rapidlei.com/api\"\r\n}"}],"_postman_id":"854db81c-729d-46a1-b651-a658bbddcef6"},{"name":"LEI – Renew LEI","id":"830c700d-8e47-46fb-840c-4561ae99c4a4","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.
\n","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity.
\n","key":"Content-Type","name":"Content-Type","type":"text","value":"application/json"}],"body":{"mode":"raw","raw":"{\r\n \"leiNumber\": \"98450024FD4543302F20\",\r\n \"isLevel1DataSame\": true,\r\n \"notificationUrl\": \"https://www.someotherserver.com/notify/me/when/lei/is/ready\",\r\n \"notificationToken\": \"Sq31YkqGWKXGEpeJGZwM\"\r\n}","options":{"raw":{"language":"json"}}},"url":"https://apitesting.rapidlei.com/v1/leis/orders/renew","description":"This API endpoint initiates the workflow process to move the ‘nextRenewalDate’ forward by 1 year. Renewal is defined as the process to verify all Level 1 & Level 2 data remains accurate on an annual basis. All LEIs not in the final year of a contract will automatically attempt renewal. Only during the last 60 days of the final year of the contract may the contract for an LEI be renewed using this API endpoint. A full list of LEIs can be obtained using the “LEI – Query Renewable LEIs” endpoint. Note that LEIs cannot be renewed unless they have either LAPSED (i.e. outside of any contract) or they are in an ISSUED state and have a ‘nextRenewalDate’ which falls within 60 days of the renewal API call.
\nleiNumberLEI Number for the Legal Entity. e.g. 98450024FD4543302F20
\nisLevel1DataSame
A Boolean value – to agree that the current LE-RD (Level 1) data is the same as the previous year. LE-RD (Level 1 data for any LEI under the management of RapidLEI can be verified using the ‘Query Level 1 LE-RD and Authorised Representative’ endpoint
notificationUrlTo avoid unnecessary polling, webhooks can be used to pass orderStatus information in real time. A webhook is a user-defined HTTP (ideally HTTPS) endpoints which can accept POST requests for real time synchronous LEI processing. An optional security token may be used to avoid replay attacks, however the notificationUrl may also contain additional URL parameters. Webhook ApS in Denmark, ran by Simon Fredsted, offers a very simple listening service for testing webhooks. Please see https://webhook.site/ for details and usage guidelines. The two parameters returned in the RequestBody are - orderTrackingCode and orderStatus, with the optional security token being returned as notificationTokene.g. https://www.someotherserver.com/notify/me/when/lei/is/ready
or https://www.someotherserver.com/notify/me/when/lei/is/ready?type=exampletype&token=URL_based_token_examplePLEASE NOTE - Redirects are not guaranteed to be supported in all cases therefore please ensure the correct URL and any final / characters in the URL are sent.
notificationTokenAn optional unique token to avoid the possibility of a third party accidentally making a call to a static notification URL and therefore maliciously affecting the workflow.
e.g. Sq31YkqGWKXGEpeJGZwM\"
userCommentsAn optional comment or instruction to aid efficient processing of the LEI by the RapidLEI vetting team – to be used primarily for simple comments < 1000 characters to avoid the need to send additional corroborating documents.
\nfirstNameThe First Name(s) of the Authorised Representative with the responsibility/authority to request and approve the creation of an LEI e.g. Peter. Only send this if the signing authority has changed in the last year.
\nlastNameThe Last Name of the Authorised Representative e.g. Anderson. Only send this if the Authorised Representative has changed in the last year.
\nmultiYearSupportAn integer from 1 to 5. Please see https://rapidlei.com/lei-pricing/ for details. Please default to 1 as the standard option.
\nloaFile
\nA Letter of Authorization (LoA) is used to provide linkage between the Applicant applying for the LEI and the empowered Authorised Representative name submitted as firstName lastName parameters. LoA's are optional as they can be replaced with appropriate Terms & Conditions. It is usual for a Registration Agent to provide T's and C's which negate the need for an LoA, however, in lieu of these being available, an LoA would be required to provide permission to the Registration Agent from the Empowered Authorised Representative. For more details please discuss with our legal team legal(a)rapidlei.com. Only 1 LoA may be submitted using either the fileData method or fileUrl method.
\ncorroboratingFiles
Up to 10 additional files which may aid vetting or validation of the Application. Please note the upload limit of 20MB each.
The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.
\n","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"key":"Content-Type","value":"application/json","description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity.
\n","type":"text"}],"url":"https://apitesting.rapidlei.com/v1/lei/orders/{orderTrackingCode}/status","description":"This API endpoint is used to check the LEI orderStatus. The bearer access Token from 'Authentication - Request Access Token' is required to submit the request and a valid 'orderTrackingCode' must be submitted within in the URL.
\nfailure\n Sent when unable to process the requested action. See message for additional details as responses vary dependent on the workflow.
\nsuccess\n Sent when actionable. Additional responses dependent on the workflow. e.g. orderTrackingCode & confidenceLevel sent in response to a successful 'New LEI' request.
\nin_progress\n The order is with RapidLEI to progress (gather data, confirm information etc)
\nstopped\n No further action can take place.
\ncomplete\n The workflow is complete. Additional responses dependent on the workflow. e.g. \"message\" & \"leiCode\" returned in response to a successfully issued, imported or renewed LEI
\npending\n LEI Confirm LE-RD Data Quality required by API
\npending_gui\n Confirmation required or additional information required – only possible via the GUI interface
\ninvalid_request\n This message is returned when mandatory parameters are missing
\nauthorization_error\n This message is returned if there's a failure due to either an invalid client_id (email address) or client_secret (API key from My Settings)
\nnot_found\n This message is returned if there's an error in the requested URL
\nunsupported_grant_type\n This message is returned when the underlying protocol for bearer tokens is not used correctly.
\nserver_error\n This message is returned when there is an unexpected issue with the workflow or permission as opposed to a missing parameter
\nThe Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.
\n","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity.
\n","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://apitesting.rapidlei.com/v1/lei/orders/{orderTrackingCode}/confirmation/{orderConfirmationStatus}","description":"This API call is used to confirm the LE-RD data quality status before an LEI can be issued. Set the correct 'orderTrackingCode' in the URL before making an API call. Also make sure you are passing either true or false while replacing the 'orderConfirmationStatus' parameter in the URL.
\nThis API call is one of the most important calls. The call is used to confirm the acceptance of the LE-RD (Legal Entity Reference Data) returned through the 'LEI - Check LEI Order status'. A Legal Entity must be presented with the LE-RD and MUST confirm the accuracy of the data. The Access Token from 'Authentication - Request Access Token' is required to submit the request and the acceptance by the Legal Entity is either 'True' - i.e. The Legal Entity agrees to and accepts the LE-RD or 'False' - i.e. There is an error which must be corrected. It is suggested that a feedback form is used to obtain details of the error. Submitting 'False' requires follow up via the RapidLEI Identity Platform GUI. Submitting 'True' requires the use of the 'LEI - Check LEI Order Status' to obtain the LEI Number.
\n","urlObject":{"protocol":"https","path":["v1","lei","orders","{orderTrackingCode}","confirmation","{orderConfirmationStatus}"],"host":["apitesting","rapidlei","com"],"query":[],"variable":[]}},"response":[{"id":"00f6aabc-1a4e-4914-84ca-2e6ab467b7e2","name":"Successful Response - Data Quality Confirmation ‘false’","originalRequest":{"method":"POST","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"}],"url":"https://apitesting.rapidlei.com/v1/lei/orders/987a9sd8f7a9sd8f7/confirmation/false"},"status":"OK","code":200,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderTrackingCode\": \"987a9sd8f7a9sd8f7\",\n \"orderStatus\": \"stopped\",\n \"message\": \"We have received confirmation of DISAGREEMENT to the LE-RD Data Quality. We are unable to continue processing this order using the API - Please login to the RapidLEI Identity Platform to continue the process via the ‘Pending’ filter.\"\n}"},{"id":"f8b5e36c-dda3-4a55-aabd-df24d423c002","name":"Successful Response - Data Quality confirmation ‘true’ (Import LEI)","originalRequest":{"method":"POST","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"}],"url":"https://apitesting.rapidlei.com/v1/lei/orders/987a9sd8f7a9sd8f7/confirmation/true"},"status":"OK","code":200,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderTrackingCode\": \"987a9sd8f7a9sd8f7\",\n \"orderStatus\": \"in_progress\",\n \"message\": \"We have received confirmation of AGREEMENT to the LE-RD Data Quality and will continue processing your order. Your LEI will be imported shortly.\"\n}"},{"id":"7c2238f4-07c0-4847-84ab-53daf8a4e4b7","name":"Successful Response - Data Quality confirmation ‘true’ (New LEI)","originalRequest":{"method":"PUT","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"key":"Content-Type","value":"application/json","description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","type":"text"}],"url":"https://apitesting.rapidlei.com/v1/lei/orders/987a9sd8f7a9sd8f7/confirmation/true"},"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderTrackingCode\": \"987a9sd8f7a9sd8f7\",\n \"orderStatus\": \"in_progress\",\n \"message\": \"We have received confirmation of AGREEMENT to the LE-RD Data Quality and will continue processing your order. Your LEI will be imported shortly.\"\n}"},{"id":"7fc175b2-0090-412e-995e-c8275c9b5d06","name":"Unsuccessful Response - LE-RD Data Quality Confirmation already received and processed","originalRequest":{"method":"POST","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"}],"url":"https://apitesting.rapidlei.com/v1/lei/orders/987a9sd8f7a9sd8f7/confirmation/true"},"status":"Internal Server Error","code":500,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\r\n \"orderTrackingCode\": \"987a9sd8f7a9sd8f7\",\r\n \"orderStatus\": \"failure\",\r\n \"message\": \"We've already received the LE-RD confirmation from you for this Legal Entity - if in doubt, please contact our support team quoting your order tracking code, which can be found in the GUI interface, by clicking on the ‘Enhanced Detail’ from the LEI list.\"\r\n}"},{"id":"a8a6b64d-11ac-49d1-a9c0-9d3d6176f3e9","name":"Unsuccessful Response - InComplete Company Profile Loaded","originalRequest":{"method":"PUT","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"key":"Content-Type","value":"application/json","description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","type":"text"}],"url":"https://apitesting.rapidlei.com/v1/lei/orders/987a9sd8f7a9sd8f7/confirmation/true"},"status":"Internal Server Error","code":500,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderTrackingCode\": \"987a9sd8f7a9sd8f7\",\n \"orderStatus\": \"failure\",\n \"message\": \"We have been unable to obtain all data from the business registry, so we are unable to continue processing using the API. Please login to the RapidLEI Identity Platform to continue the process.\"\n}"},{"id":"185e71b4-a2d4-4c01-b9b3-b7f01f786cfe","name":"Successful Response - Contract terms agreed but LE-RR Level 2 data is required","originalRequest":{"method":"POST","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"}],"url":"https://apitesting.rapidlei.com/v1/lei/orders/987a9sd8f7a9sd8f7/confirmation/true"},"status":"OK","code":200,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{ \r\n \"orderTrackingCode\": \"987a9sd8f7a9sd8f7\", \r\n \"orderStatus\": \"pending\", \r\n \"message\": \"We are unable to continue processing this order using the API - Please login to the RapidLEI Identity Platform to continue the process.\" \r\n}"},{"id":"465ca85a-214c-4473-897b-37b556b3a254","name":"Unsuccessful Response - Company Profile Not Loaded","originalRequest":{"method":"PUT","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"key":"Content-Type","value":"application/json","description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","type":"text"}],"url":"https://apitesting.rapidlei.com/v1/lei/orders/987a9sd8f7a9sd8f7/confirmation/true"},"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\r\n \"orderTrackingCode\": \"987a9sd8f7a9sd8f7\",\r\n \"orderStatus\": \"failure\",\r\n \"message\": \"Operation not allowed. Please use the Check Order Status API.\"\r\n}"},{"id":"567ee570-9194-4de3-b3f8-c86860c91a5c","name":"Unsuccessful Response - 'orderConfirmationStatus' must be true or false","originalRequest":{"method":"POST","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"}],"url":"https://apitesting.rapidlei.com/v1/lei/orders/987a9sd8f7a9sd8f7/confirmation/asdf"},"status":"Bad Request","code":400,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderStatus\": \"invalid_request\",\n \"message\": \"Request parameter 'orderConfirmationStatus' should contain a Boolean value of either 'true' or 'false'\",\n \"errorUri\": \"https://rapidlei.com/api\"\n}"},{"id":"583a05ec-ef76-461f-aca8-f07a9307edab","name":"Unsuccessful Response - Unknown error OR Exception during processing request","originalRequest":{"method":"POST","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"}],"url":"https://apitesting.rapidlei.com/v1/lei/orders/987a9sd8f7a9sd8f7/confirmation/true"},"status":"Internal Server Error","code":500,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderStatus\": \"server_error\",\n \"message\": \"We've been unable to process your request - please contact our support team quoting your order tracking code, which can be found in the GUI interface, by clicking on the ‘Enhanced Detail’ from the LEI list.\",\n \"errorUri\": \"https://rapidlei.com/api\"\n}"},{"id":"b4589f2d-7003-49ae-91af-46f0b3921a3a","name":"Successful Response – Data Quality Pre–Check and Duplicate API calls are being made to the GLEIS for new LEIs","originalRequest":{"method":"POST","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"}],"url":"https://api.rapidlei.com/v1/lei/orders/987a9sd8f7a9sd8f7/confirmation/true"},"status":"OK","code":200,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\r\n \"orderTrackingCode\": \"987a9sd8f7a9sd8f7\",\r\n \"orderStatus\": \"in_progress\",\r\n \"message\": \" You've submitted the Data Duality Confirmation at the point we are doing a Check for Duplicates (C4D) call to the GLEIS. These can take between 15 and 45 seconds. We've acknowledged your confirmation of the profile accuracy, so you do not need to submit again.\"\r\n}"},{"id":"ae51f26b-6ad1-408c-b6d2-7eb4edd4b1c3","name":"Successful Response – Data Quality Pre–Check calls are being made to the GLEIS for imported LEIs","originalRequest":{"method":"POST","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"}],"url":"https://api.rapidlei.com/v1/lei/orders/987a9sd8f7a9sd8f7/confirmation/true"},"status":"OK","code":200,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\r\n \"orderTrackingCode\": \"987a9sd8f7a9sd8f7\",\r\n \"orderStatus\": \"in_progress\",\r\n \"message\": \" You've submitted the Data Duality Confirmation at the point we are doing a Check for Duplicates (C4D) call to the GLEIS. These can take between 15 and 45 seconds. We've acknowledged your confirmation of the profile accuracy, so you do not need to submit again.\"\r\n}"}],"_postman_id":"b932bc45-0ef2-4810-ba9a-a3c31431d2bb"},{"name":"LEI - Query all LEIs","id":"60165053-3b7d-4ffc-8f87-7ee79ab06b14","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"GET","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.
\n","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity.
\n","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://apitesting.rapidlei.com/v1/leis/orders","description":"This API is used to query for a list of ALL LEIs which have been successfully issued (Created or Imported) from the account. This includes shopping cart and XLS based bulk workflows. Any LEI which has not yet been issued, but has been created by API calls can be verified individually by the 'LEI - Check Order Status' call. Any requests made via the shopping cart or xls methods may be tracked from within the browser based UI by logging in to the https://lei.rapidlei.com/Account/Login. The Access Token from 'Authentication - Request Access Token' is required to submit the request.
\nPlease note that this API call DOES NOT return LEI numbers if the LEI has been marked as a DUPLICATE, ANULLED, MERGED or RETIRED.
\nOnly LEIs with a registration status of ISSUED or LAPSED will be returned.
\nReviewing LEI-RD (Reference data) is possible via the LEI number and the GLEIF API call. https://www.gleif.org/en/lei-data/gleif-lei-look-up-api/access-the-api
\n","urlObject":{"protocol":"https","path":["v1","leis","orders"],"host":["apitesting","rapidlei","com"],"query":[],"variable":[]}},"response":[{"id":"802cf7e2-fdef-4355-a633-b394e680e5e9","name":"Successful Response – List of LEIs returned","originalRequest":{"method":"GET","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://apitesting.rapidlei.com/v1/leis/orders"},"status":"OK","code":200,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\r\n \"new\": [\r\n \"984500049401E2B8D492\",\r\n \"984500049401E2B8D491\",\r\n \"984500049401E2B8D494\"\r\n ],\r\n \"imported\": [\r\n \"213800MAKC4IOK7LEH11\",\r\n \"213800MAKC4IOK7LEH12\",\r\n \"213800MAKC4IOK7LEH13\"\r\n ]\r\n}"},{"id":"211af1cf-289b-43dd-bb92-05e81652156e","name":"Unsuccessful Response – Unknown Error or Exception during processing request","originalRequest":{"method":"GET","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://apitesting.rapidlei.com/v1/leis/orders"},"status":"Internal Server Error","code":500,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderStatus\": \"server_error\",\n \"message\": \" We've been unable to process your request – please contact our support team.\",\n \"errorUri\": \"https://rapidlei.com/api\"\n}"},{"id":"a09fea26-f10d-4491-996c-289e7e0b6b11","name":"Unsuccessful Response – User not allowed to use the Full API, only the ‘Create User’ endpoint","originalRequest":{"method":"GET","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://apitesting.rapidlei.com/v1/leis/orders"},"status":"Unauthorized","code":401,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderStatus\": \"authorization_error\",\n \"message\": \"You do not have the ability to use the Full RapidLEI API from this account – you are configured only to use the ‘Create User’ endpoint, please contact our support team on support@rapidlei.com\",\n \"errorUri\": \"https://rapidlei.com/api\"\n}"}],"_postman_id":"60165053-3b7d-4ffc-8f87-7ee79ab06b14"},{"name":"LEI – Query Lapsed LEIs","id":"baefab80-254c-4c14-9548-5bdb41859443","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"GET","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.
\n","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity.
\n","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://apitesting.rapidlei.com/v1/leis/orders/lapsed","description":"This API call is used to query all LAPSED LEIs.
\n","urlObject":{"protocol":"https","path":["v1","leis","orders","lapsed"],"host":["apitesting","rapidlei","com"],"query":[],"variable":[]}},"response":[{"id":"f9f7daa3-141b-4b20-9468-283a4b76fb4e","name":"Successful Response – List of LEIs and nextRenewalDate’s returned","originalRequest":{"method":"GET","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://apitesting.rapidlei.com/v1/leis/orders/lapsed"},"status":"OK","code":200,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"[\n {\n \"leiNumber\": \"14955838975411027285\",\n \"nextRenewalDate\": \"2021-07-09T11:54:35+00:00\"\n },\n {\n \"leiNumber\": \"984500EFP7C0E4CEA733\",\n \"nextRenewalDate\": \"2021-07-29T11:54:35+00:00\"\n },\n {\n \"leiNumber\": \"984500801560A0481F75\",\n \"nextRenewalDate\": \"2021-07-09T11:54:35+00:00\"\n }\n]"},{"id":"b70a7f55-6162-4fb9-a1d2-b6ab32fa225d","name":"Unsuccessful Response – User not allowed to use the Full API, only the ‘Create User’ endpoint","originalRequest":{"method":"GET","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://apitesting.rapidlei.com/v1/leis/orders/lapsed"},"status":"Unauthorized","code":401,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderStatus\": \"authorization_error\",\n \"message\": \"You do not have the ability to use the Full RapidLEI API from this account – you are configured only to use the ‘Create User’ endpoint, please contact our support team on support@rapidlei.com\",\n \"errorUri\": \"https://rapidlei.com/api\"\n}"},{"id":"d8060f42-163d-4068-9d5e-519d9d3890ff","name":"Unsuccessful Response – Unknown Error or Exception during processing request","originalRequest":{"method":"GET","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://apitesting.rapidlei.com/v1/leis/orders/lapsed"},"status":"Internal Server Error","code":500,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderStatus\": \"server_error\",\n \"message\": \" We've been unable to process your request - please contact our support team.\",\n \"errorUri\": \"https://rapidlei.com/api\"\n}"}],"_postman_id":"baefab80-254c-4c14-9548-5bdb41859443"},{"name":"LEI – Query Renewable LEIs","id":"686a1f79-f42a-4b40-838d-13099bba25a7","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"GET","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.
\n","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity.
\n","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://apitesting.rapidlei.com/v1/leis/orders/renew/{days}","description":"This API call is used to query all LEIs which may be renewed within the next {days}. The parameter \"days\" is a numeric value between 1 and 60. Ideally values of 15, 30, 45 or 60 are passed to mirror the GUI DASHBOARD Interface. Please note that multi-year LEIs will automatically renew 60 days prior to the “nextRenewalDate” and are therefore excluded from the returned list. The exception being any LEI with Level 2 data or any ESO based FUND which cannot be verified by the RapidLEI vetting team - these will appear too.
\n","urlObject":{"protocol":"https","path":["v1","leis","orders","renew","{days}"],"host":["apitesting","rapidlei","com"],"query":[],"variable":[]}},"response":[{"id":"ae4e3116-4361-45aa-b5cd-d42a4e08e1a1","name":"Successful Response – List of LEIs and nextRenewalDate’s returned","originalRequest":{"method":"GET","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://apitesting.rapidlei.com/v1/leis/orders/renew/60"},"status":"OK","code":200,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"[\n {\n \"leiNumber\": \"14955838975411027285\",\n \"nextRenewalDate\": \"2021-07-09T11:54:35+00:00\"\n },\n {\n \"leiNumber\": \"984500EFP7C0E4CEA733\",\n \"nextRenewalDate\": \"2021-07-29T11:54:35+00:00\"\n },\n {\n \"leiNumber\": \"984500801560A0481F75\",\n \"nextRenewalDate\": \"2021-07-09T11:54:35+00:00\"\n }\n]"},{"id":"89839109-1cb5-4d79-9a8b-4d73a0690ccd","name":"Unsuccessful Response – User not allowed to use the Full API, only the ‘Create User’ endpoint","originalRequest":{"method":"GET","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://apitesting.rapidlei.com/v1/leis/orders/renew/60"},"status":"Unauthorized","code":401,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderStatus\": \"authorization_error\",\n \"message\": \"You do not have the ability to use the Full RapidLEI API from this account – you are configured only to use the ‘Create User’ endpoint, please contact our support team on support@rapidlei.com\",\n \"errorUri\": \"https://rapidlei.com/api\"\n}"},{"id":"e2d21a34-3069-49e2-9ef5-f601cdf105e7","name":"Unsuccessful Response – Unknown Error or Exception during processing request","originalRequest":{"method":"GET","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://apitesting.rapidlei.com/v1/leis/orders/renew/60"},"status":"Internal Server Error","code":500,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderStatus\": \"server_error\",\n \"message\": \" We've been unable to process your request - please contact our support team.\",\n \"errorUri\": \"https://rapidlei.com/api\"\n}"},{"id":"82d598d9-fe50-428c-8259-034854652eb4","name":"Unsuccessful Response – Invalid or nonnumeric days parameter","originalRequest":{"method":"GET","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://apitesting.rapidlei.com/v1/leis/orders/renew/100"},"status":"Bad Request","code":400,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderStatus\": \"invalid_request\",\n \"message\": \"Request parameter ‘days’ should contain a numeric value between 1 and 60\",\n \"errorUri\": \"https://rapidlei.com/api\"\n}"}],"_postman_id":"686a1f79-f42a-4b40-838d-13099bba25a7"},{"name":"LEI – Query Level 1 LE-RD and Authorised Representative","id":"011e1d73-8f3b-4fe0-9a6b-1ffd69ada2ce","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"GET","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.
\n","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity.
\n","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://apitesting.rapidlei.com/v1/leis/level1/{leiNumber}","description":"This API call is used to query Level 1 (LE-RD) data for any LEI managed by RapidLEI
\n","urlObject":{"protocol":"https","path":["v1","leis","level1","{leiNumber}"],"host":["apitesting","rapidlei","com"],"query":[],"variable":[]}},"response":[{"id":"a83f45c8-17e5-45c5-84a3-6757ba29f313","name":"Successful Response – LEI Level 1 LE-RD and Authorised Representative data available","originalRequest":{"method":"GET","header":[{"key":"Authorization","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx","description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","type":"text"},{"key":"Content-Type","value":"application/json","description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","type":"text"}],"url":"https://apitesting.rapidlei.com/v1/leis/level1/529900T8BM49AURSDO55"},"status":"OK","code":200,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"signingAuthorityName\": \"Paul Tourret\",\n \"referenceData\": {\n \"leiNumber\": \"529900T8BM49AURSDO55\",\n \"legalName\": \"Ubisecure Oy\",\n \"legalNameLanguage\": \"fi\",\n \"registrationAuthorityEntityId\": \"1748721–4\",\n \"entityLegalFormCode\": \"DKUW\",\n \"entityLegalForm\": null,\n \"entityLegalFormLanguage\": \"FI\",\n \"entityStatus\": \"ACTIVE\",\n \"registrationAuthorityId\": \"RA000188\",\n \"registrationAuthority\": null,\n \"entityCategory\": \"GENERAL\",\n \"entityCreationDate\" : \"2002-02-14T00:00:00+00:00\",\n \"legalJurisdiction\": \"FI\",\n \"initialRegistrationDate\": \"2016–08–04T11:00:36+00:00\",\n \"nextRenewalDate\": \"2025–12–20T12:23:13+00:00\",\n \"lastUpdateDate\": \"2024–12–20T12:23:13+00:00\",\n \"registrationStatus\": \"ISSUED\",\n \"validationSource\": \"FULLY_CORROBORATED\",\n \"managingLOU\": \"529900T8BM49AURSDO55\",\n \"successorLEI\": null,\n \"successorEntityName\": null,\n \"contractExpiryDate\": \"2028-01-21T21:54:37+00:00\",\n \"otherEntityNames\": [\n {\n \"type\": \"TRADING_OR_OPERATING_NAME\",\n \"value\": \"Ubisecure Inc\",\n \"language\": \"FI\"\n },\n {\n \"type\": \"TRADING_OR_OPERATING_NAME\",\n \"value\": \"Ubisecure Ab\",\n \"language\": \"SV\"\n }\n ],\n \"transliteratedOtherEntityNames\": [],\n \"legalAddress\": {\n \"mailRouting\": null,\n \"firstAddressLine\": \"Vaisalantie 2\",\n \"addressLine1\": null,\n \"addressLine2\": null,\n \"addressLine3\": null,\n \"city\": \"Espoo\",\n \"state\": null,\n \"country\": \"FI\",\n \"postalCode\": \"02130\"\n },\n \"transliertatedLegalAddress\": null,\n \"headquartersAddress\": {\n \"mailRouting\": null,\n \"firstAddressLine\": \"Tekniikantie 14\",\n \"addressLine1\": null,\n \"addressLine2\": null,\n \"addressLine3\": null,\n \"city\": \"Espoo\",\n \"state\": null,\n \"country\": \"FI\",\n \"postalCode\": \"02150\"\n },\n \"transliteratedHeadquartersAddress\": null,\n \"validationAuthority\": {\n \"validationAuthorityID\": \"RA000188\",\n \"otherValidationAuthorityID\": null,\n \"validationAuthorityEntityID\": \"1748721–4\"\n },\n \"otherValidationAuthorities\": []\n }\n} "},{"id":"a916cc08-e713-4f99-8561-618ecbaef906","name":"Unsuccessful Response – LEI not managed by your RapidLEI account","originalRequest":{"method":"GET","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://apitesting.rapidlei.com/v1/leis/level1/529900T8BM49AURSDO55"},"status":"Internal Server Error","code":500,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderStatus\": \"failure\",\n \"message\": \"The LEI number requested is not managed by your RapidLEI account. Please provide a valid LEI Number or contact our support team to discuss options.\"\n}"},{"id":"d33472f7-5994-467a-815c-b1c7c3e745e0","name":"Unsuccessful Response – Level 1 data is not currently available","originalRequest":{"method":"GET","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://apitesting.rapidlei.com/v1/leis/level1/529900T8BM49AURSDO55"},"status":"Internal Server Error","code":500,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderStatus\": \"failure\",\n \"message\": \" The LEI must be either ISSUED, LASPED, DUPLICATE, PENDING_TRANSFER, PENDING_ARCHIVAL, RETIRED or MERGED for level 1 data to be available. LEIs which are ‘pending’, ‘pending_gui’ or ‘in_progress’ may not be queried.\"\n}"},{"id":"94c1261a-dec0-4711-869a-dcad9b40b820","name":"Unsuccessful Response – Invalid LEI Format","originalRequest":{"method":"GET","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://apitesting.rapidlei.com/v1/leis/level1/529900T8BM49A"},"status":"Bad Request","code":400,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderStatus\": \"invalid_request\",\n \"message\": \"Please ensure the 'lei' is a valid ISO 17442 format LEI (20 characters).\",\n \"errorUri\": \"https://rapidlei.com/api\"\n}"},{"id":"4627394a-4b9e-422e-bdcb-ec748d7b607c","name":"Unsuccessful Response – User not allowed to use the Full API, only the ‘Create User’ endpoint","originalRequest":{"method":"GET","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://apitesting.rapidlei.com/v1/leis/level1/529900T8BM49AURSDO55"},"status":"Unauthorized","code":401,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderStatus\": \"authorization_error\",\n \"message\": \"You do not have the ability to use the Full RapidLEI API from this account – you are configured only to use the ‘Create User’ endpoint, please contact our support team on support@rapidlei.com\",\n \"errorUri\": \"https://rapidlei.com/api\"\n}"},{"id":"c21a5c8b-5786-4f90-b810-fce66c3e9526","name":"Unsuccessful Response – Unknown Error or Exception during processing request","originalRequest":{"method":"GET","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://apitesting.rapidlei.com/v1/leis/level1/529900T8BM49AURSDO55"},"status":"Internal Server Error","code":500,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderStatus\": \"server_error\",\n \"message\": \" We've been unable to process your request - please contact our support team.\",\n \"errorUri\": \"https://rapidlei.com/api\"\n}"}],"_postman_id":"011e1d73-8f3b-4fe0-9a6b-1ffd69ada2ce"},{"name":"LEI – Query Level 2 LE-RR, LE-RE and PNI data","id":"13b06868-4eb9-4281-aa59-c4b089e69aaf","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"GET","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.
\n","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity.
\n","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://apitesting.rapidlei.com/v1/leis/level2/{leiNumber}","description":"This API call is used to query Level 2 (LE-RR) data for any LEI managed by RapidLEI. This includes, relationship data, exception reporting and if level 2 parents do not have LEIs, PNI data.
\n","urlObject":{"protocol":"https","path":["v1","leis","level2","{leiNumber}"],"host":["apitesting","rapidlei","com"],"query":[],"variable":[]}},"response":[{"id":"3027a6f1-72b9-46da-b21a-5ef20f1822c4","name":"Successful Response – Level 2 data has Reporting Exceptions ","originalRequest":{"method":"GET","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://apitesting.rapidlei.com/v1/leis/level2/984500B8IBDAB46C3750"},"status":"OK","code":200,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"relationshipRecords\": [],\n \"reportingExceptions\": [\n {\n \"lei\": \"984500B8IBDAB46C3750\",\n \"exceptionCategory\": \"DIRECT_ACCOUNTING_CONSOLIDATION_PARENT\",\n \"exceptionReason\": \"NATURAL_PERSONS\",\n \"exceptionReference\": null\n },\n {\n \"lei\": \"984500B8IBDAB46C3750\",\n \"exceptionCategory\": \"ULTIMATE_ACCOUNTING_CONSOLIDATION_PARENT\",\n \"exceptionReason\": \"NATURAL_PERSONS\",\n \"exceptionReference\": null\n }\n ],\n \"parentReferenceRecords\": []\n}"},{"id":"7b695a56-0977-4a9a-a6e3-afec7c5d1c38","name":"Successful Response – Level 2 data has Relationship Records","originalRequest":{"method":"GET","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://apitesting.rapidlei.com/v1/leis/level2/984500B8IBDAB46C3750"},"status":"OK","code":200,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"relationshipRecords\": [\n {\n \"startNode\": {\n \"nodeID\": \"529900T8BM49AURSDO55\",\n \"nodeIDType\": \"LEI\"\n },\n \"endNode\": {\n \"nodeID\": \"89450051ZRDOL9KEWH63\",\n \"nodeIDType\": \"LEI\"\n },\n \"relationshipType\": \"IS_DIRECTLY_CONSOLIDATED_BY\",\n \"relationshipStatus\": \"ACTIVE\",\n \"initialRegistrationDate\": \"2018-05-08T18:15:52+00:00\",\n \"lastUpdateDate\": \"2021-02-20T12:23:13+00:00\",\n \"nextRenewalDate\": \"2022-12-20T12:23:13+00:00\",\n \"registrationStatus\": \"PUBLISHED\",\n \"managingLOU\": \"529900T8BM49AURSDO55\",\n \"validationSources\": \"FULLY_CORROBORATED\",\n \"validationDocuments\": \"ACCOUNTS_FILING\",\n \"validationReference\": null,\n \"relationshipQualifier\": {\n \"qualifierDimension\": \"ACCOUNTING_STANDARD\",\n \"qualifierCategory\": \"OTHER_ACCOUNTING_STANDARD\"\n },\n \"relationshipQuantifier\": {\n \"measurementMethod\": \"ACCOUNTING_CONSOLIDATION\",\n \"quantifierAmount\": 100,\n \"quantifierUnits\": \"PERCENTAGE\"\n },\n \"relationshipPeriods\": [\n {\n \"startDate\": \"2021-01-01T00:00:00+00:00\",\n \"endDate\": \"2021-12-31T00:00:00+00:00\",\n \"periodType\": \"ACCOUNTING_PERIOD\"\n },\n {\n \"startDate\": \"2018-05-17T00:00:00+00:00\",\n \"endDate\": null,\n \"periodType\": \"RELATIONSHIP_PERIOD\"\n }\n ]\n },\n {\n \"startNode\": {\n \"nodeID\": \"529900T8BM49AURSDO55\",\n \"nodeIDType\": \"LEI\"\n },\n \"endNode\": {\n \"nodeID\": \"89450051ZRDOL9KEWH63\",\n \"nodeIDType\": \"LEI\"\n },\n \"relationshipType\": \"IS_ULTIMATELY_CONSOLIDATED_BY\",\n \"relationshipStatus\": \"ACTIVE\",\n \"initialRegistrationDate\": \"2018-05-08T18:15:52+00:00\",\n \"lastUpdateDate\": \"2021-02-20T12:23:13+00:00\",\n \"nextRenewalDate\": \"2022-12-20T12:23:13+00:00\",\n \"registrationStatus\": \"PUBLISHED\",\n \"managingLOU\": \"529900T8BM49AURSDO55\",\n \"validationSources\": \"FULLY_CORROBORATED\",\n \"validationDocuments\": \"ACCOUNTS_FILING\",\n \"validationReference\": null,\n \"relationshipQualifier\": {\n \"qualifierDimension\": \"ACCOUNTING_STANDARD\",\n \"qualifierCategory\": \"OTHER_ACCOUNTING_STANDARD\"\n },\n \"relationshipQuantifier\": {\n \"measurementMethod\": \"ACCOUNTING_CONSOLIDATION\",\n \"quantifierAmount\": 100,\n \"quantifierUnits\": \"PERCENTAGE\"\n },\n \"relationshipPeriods\": [\n {\n \"startDate\": \"2021-01-01T00:00:00+00:00\",\n \"endDate\": \"2021-12-31T00:00:00+00:00\",\n \"periodType\": \"ACCOUNTING_PERIOD\"\n },\n {\n \"startDate\": \"2018-05-17T00:00:00+00:00\",\n \"endDate\": null,\n \"periodType\": \"RELATIONSHIP_PERIOD\"\n }\n ]\n }\n ],\n \"reportingExceptions\": [],\n \"parentReferenceRecords\": []\n}"},{"id":"dcdd99d1-2552-4643-b13e-9b9c466067da","name":"Successful Response – Level 2 data has Parent Reference Data (PNI) ","originalRequest":{"method":"GET","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://apitesting.rapidlei.com/v1/leis/level2/984500B8IBDAB46C3750"},"status":"OK","code":200,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"relationshipRecords\": [],\n \"reportingExceptions\": [\n {\n \"lei\": \"984500B8IBDAB46C3750\",\n \"exceptionCategory\": \"DIRECT_ACCOUNTING_CONSOLIDATION_PARENT\",\n \"exceptionReason\": \"NO_LEI\",\n \"exceptionReference\": null\n },\n {\n \"lei\": \"984500B8IBDAB46C3750\",\n \"exceptionCategory\": \"ULTIMATE_ACCOUNTING_CONSOLIDATION_PARENT\",\n \"exceptionReason\": \"NO_LEI\",\n \"exceptionReference\": null\n }\n ],\n \"parentReferenceRecords\": [\n {\n \"legalName\": \"UBISECURE HOLDINGS LIMITED\",\n \"registrationAuthorityEntityId\": \"10408185\",\n \"legalJurisdiction\": \"GB–ENG\",\n \"parentType\": \"DIRECT_PARENT\"\n },\n {\n \"legalName\": \"UBISECURE HOLDINGS LIMITED\",\n \"legalNameLanguage\": \"en\",\n \"registrationAuthorityEntityId\": \"10408185\",\n \"legalJurisdiction\": \"GB–ENG\",\n \"parentType\": \"ULTIMATE_PARENT\"\n }\n ]\n}"},{"id":"b3cff772-98c5-40dc-999b-092057b6140a","name":"Successful Response – Level 2 Fund Reporting","originalRequest":{"method":"GET","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://apitesting.rapidlei.com/v1/leis/level2/984500B8IBDAB46C3750"},"status":"OK","code":200,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"relationshipRecords\": [\n {\n \"startNode\": {\n \"nodeID\": \"529900T8BM49AURSDO55\",\n \"nodeIDType\": \"LEI\"\n },\n \"endNode\": {\n \"nodeID\": \"89450051ZRDOL9KEWH63\",\n \"nodeIDType\": \"LEI\"\n },\n \"relationshipType\": \"IS_FEEDER_TO\",\n \"relationshipStatus\": \"ACTIVE\",\n \"initialRegistrationDate\": \"2021–12–20T12:23:13+00:00\",\n \"lastUpdateDate\": \"2021–12–20T12:23:13+00:00\",\n \"nextRenewalDate\": \"2022–12–20T12:23:13+00:00\",\n \"registrationStatus\": \"PUBLISHED\",\n \"managingLOU\": \"529900T8BM49AURSDO55\",\n \"validationSources\": \"ENTITY_SUPPLIED_ONLY\",\n \"validationDocuments\": \"ACCOUNTS_FILING\",\n \"validationReference\": \"https://www.fund-data-reference-example.com\",\n \"relationshipPeriods\": [\n {\n \"startDate\": \"2020-01-14T00:00:00+00:00\",\n \"endDate\": null,\n \"periodType\": \"RELATIONSHIP_PERIOD\"\n }\n ]\n }\n ],\n \"reportingExceptions\": [\n {\n \"lei\": \"529900T8BM49AURSDO55\",\n \"exceptionCategory\": \"DIRECT_ACCOUNTING_CONSOLIDATION_PARENT\",\n \"exceptionReason\": \"NON_CONSOLIDATING\",\n \"exceptionReference\": null\n },\n {\n \"lei\": \"529900T8BM49AURSDO55\",\n \"exceptionCategory\": \"ULTIMATE_ACCOUNTING_CONSOLIDATION_PARENT\",\n \"exceptionReason\": \"NON_CONSOLIDATING\",\n \"exceptionReference\": null\n }\n ],\n \"parentReferenceRecords\": []\n}"},{"id":"f2ecec66-f8d9-4cf0-bb86-dc269b2fef3f","name":"Unsuccessful Response – LEI not managed by your RapidLEI account","originalRequest":{"method":"GET","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://apitesting.rapidlei.com/v1/leis/level2/984500B8IBDAB46C3750"},"status":"Internal Server Error","code":500,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderStatus\": \"failure\",\n \"message\": \"The LEI number requested is not managed by your RapidLEI account. Please provide a valid LEI Number or contact our support team to discuss options.\"\n}"},{"id":"c1c99dc1-88f0-463d-9391-bc80e422c98d","name":"Unsuccessful Response – Level 2 data is not currently available","originalRequest":{"method":"GET","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://apitesting.rapidlei.com/v1/leis/level2/984500B8IBDAB46C3750"},"status":"Internal Server Error","code":500,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderStatus\": \"failure\",\n \"message\": \" The LEI must be either ISSUED, LASPED, DUPLICATE, PENDING_TRANSFER, PENDING_ARCHIVAL, RETIRED or MERGED for level 2 data to be available. LEIs which are ‘pending’, ‘pending_gui’ or ‘in_progress’ may not be queried.\"\n}"},{"id":"cba656ac-b3ed-4db7-bfb5-6df5ae74309a","name":"Unsuccessful Response – Invalid LEI Format","originalRequest":{"method":"GET","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://apitesting.rapidlei.com/v1/leis/level2/984500B8"},"status":"Bad Request","code":400,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderStatus\": \"invalid_request\",\n \"message\": \"Please ensure the 'lei' is a valid ISO 17442 format LEI (20 characters).\",\n \"errorUri\": \"https://rapidlei.com/api\"\n}"},{"id":"1810f7df-8ed3-4667-a81a-df7897cfd2f7","name":"Unsuccessful Response – User not allowed to use the Full API, only the ‘Create User’ endpoint","originalRequest":{"method":"GET","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://apitesting.rapidlei.com/v1/leis/level2/984500B8IBDAB46C3750"},"status":"Unauthorized","code":401,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderStatus\": \"authorization_error\",\n \"message\": \"You do not have the ability to use the Full RapidLEI API from this account – you are configured only to use the ‘Create User’ endpoint, please contact our support team on support@rapidlei.com\",\n \"errorUri\": \"https://rapidlei.com/api\"\n}"},{"id":"0f1bb621-3654-479f-bb99-c842b85d0873","name":"Unsuccessful Response – Unknown Error or Exception during processing request","originalRequest":{"method":"GET","header":[{"description":"The Bearer token is a cryptic string, usually generated by the server in response to a token request. The client must send this token in the Authorization header for every API call.","key":"Authorization","type":"text","value":"Bearer xxxxxxPaste_Bearer_Access_Token_herexxxxxx"},{"description":"The Content-Type header is used by HTTP clients to tell the server what content types they'll accept. The Content-Type header field is used to specify the nature of the data in the body of an entity. ","key":"Content-Type","type":"text","value":"application/json"}],"url":"https://apitesting.rapidlei.com/v1/leis/level2/984500B8IBDAB46C3750"},"status":"Internal Server Error","code":500,"_postman_previewlanguage":"json","header":[],"cookie":[],"responseTime":null,"body":"{\n \"orderStatus\": \"server_error\",\n \"message\": \" We've been unable to process your request - please contact our support team.\",\n \"errorUri\": \"https://rapidlei.com/api\"\n}"}],"_postman_id":"13b06868-4eb9-4281-aa59-c4b089e69aaf"}],"id":"a3b0d97b-66fb-4cb8-8ea3-97c6fa717b7e","description":"Version - September 2025
\nRapidLEI API endpoints have been designed to facilitate efficient workflows enabling Registration Agents, Validation Agents, and Enterprise's to 'Create New LEIs', 'Import Existing LEIs' or 'Renew LEIs'.
\nWith the exception of 'API Health Check', which requires no Authentication, RFC 6750 OAuth 2.0 Bearer Token Authentication is used in all cases. API Key(s) used to create Bearer Token(s) via the 'Authentication - Request Access Token' endpoint are managed in 'My Settings' in RapidLEI accounts with extended privileges.
\nCredentials for our 'Testing' system are not available for external parties. Please read the 'Staging' Platform documentation for details on how to apply for credentials to test our APIs or talk to our team on partnerships@rapidlei.com
\nThese API(s) are for using by RapidLEI for internal testing - If you are reading this, then yes, you'll most likely be seeing a sneak preview of what's coming down the line - enjoy ;-)
\nThe RapidLEI API is designed to avoid unnecessary polling. Whenever possible, please use the built-in 'Push Notifications' system (Details given below). Status updates, enabling polling logic workflow optimizations, are returned via the orderStatus token, whereas optional, human readable feedback from the vetting team on why an LEI order has paused is available from the adminMessage token e.g. *\"The Business Registry is currently offline – We are unable to continue processing this order until it reopens.\"*
\nin_progress
The order is with RapidLEI to progress (gather data, confirm information etc)
stopped
No further action can take place.
complete
The workflow is complete. Additional responses dependent on the workflow. e.g. \"message\" & \"leiCode\" returned in response to a successfully issued, imported or renewed LEI
pending
LEI Confirm LE-RD Data Quality required by API
pending_gui
Confirmation required or additional information required – only possible via the GUI interface
invalid_request
This message is returned when mandatory parameters are missing
authorization_error
This message is returned if there's a failure due to either an invalid client_id (email address) or client_secret (API key from My Settings)
not_found
This message is returned if there's an error in the requested URL
unsupported_grant_type
This message is returned when the underlying protocol for bearer tokens is not used correctly.
server_error
This message is returned when there is an unexpected issue with the workflow or permission as opposed to a missing parameter
Push Notifications, aka webhooks are *\"user-defined callbacks made with HTTP\"* (ideally HTTPS) endpoints which can accept POST requests. An optional security token may be used to avoid replay attacks, however the notificationUrl may also contain additional URL parameters. Webhook ApS in Denmark, ran by Simon Fredsted, offers a very simple listening service for testing webhooks. Please see https://webhook.site/ for details and usage guidelines.
The two parameters returned in the RequestBody are - orderTrackingCode and orderStatus, with the optional security token being returned as notificationToken within the Header.
profile_loaded
Sent as soon as our platform obtains the profile from the business registry. In the event of a failure, or an incomplete profile being received, our vetting team adds the missing items the registry did not provide and at this point we send profile_loaded. This can be minutes or hours depending on the jurisdiction/registry. Please use 'LEI - Check Order Status' to verify the profile's accuracy. Either verify the returned profile against data previously provided by the Applicant, or use this data to confirm the accuracy with the Applicant in a post processing workflow.
lei_issued
Sent once the LEI is ISSUED and all checks are complete including the Authority Check. (Please note that we do not send a notification for a ‘Pre-Authority LEI number’). Please use 'LEI - Check Order Status' to obtain the LEI number and the nextRenewalDate.
lei_imported
Sent once the LEI is IMPORTED and all checks are complete including the Authority Check. Please use 'LEI - Check Order Status' to obtain the LEI number and the nextRenewalDate.
lei_cancelled
Sent after a cancellation from either our Admin team or the GUI interface. (Cancellation by API is not supported)
lei_pending_gui
Sent once an edge case is identified and control is returned to the GUI Interface.
lei_duplicate_found
A potential Duplicate has been identified by a GLEIF API call and our team are investigating.
lei_pre_check_api
A pre–check API call to GLEIF has failed – RapidLEI will be investigating and correcting any issues.
lei_renewed
Sent once the LEI is renewed and all checks are complete. Please use 'LEI - Check Order Status' to obtain the LEI number and the nextRenewalDate.
lei_published
Sent once the LEI has been successfully uploaded to the GLEIS during one of the 10 daily publication cycles. For a new LEI, or changes to an existing LEI to be visible, additional time must be allowed for the GLEIF to process the data and publish to the Concatenated files, Golden Copy files & LEI Search 2.0 system – this ranges between 2 and 8 hours of our publication time.
lou_import_requested
Sent when the request to the SENDING LOU has been made. The SENDING_LOU, in response, should flip the GLEIF LEI Status from ISSUED/LASPED to PENDING_TRANSFER within 3 days indicating the request is received and that they are talking to their client.
lou_import_request_acknowledged
Sent when the GLEIF LEI Status flips to PENDING_TRANSFER. The SENDING_LOU then has 4 days to confirm the acceptance or rejection of the request.
lou_rejected
Sent after receiving a rejection from the SENDING LOU during transfer by a GLEIF LEI Status change back to LASPED/ISSUED.
lei_transferred
Sent after an LEI has successfully been transferred. i.e from RapidLEI (as the Sending LOU) to the Receiving LOU. This status will only appear when the Receiving LOU publishes the LEI to the GLEIS.
The maximum allowed FileName length (including an extension) = 250 characters e.g. \"FileName\":\"This is an example file name which shows the extent possible within the RapidLEI API eco system for Ubisecure Oy with LEI Code 529900T8BM49AURSDO55 - The remaining characters up to 250 being these... 4567890123456789012345678901234567890123456789.pdf”
\nThe maximum allowed FileURL length (including an extension) = 1000 characters e.g. \"FileURL\":\"https://someexamplefileserver.com/attachements/rapidlei/ BNVcyW5rbFdjYzAwekdONHhMU1hMbFBoWFV0bXBra2FuQ1dzUWVMYWoyRUJoU3huRFhpZnVENExhaERBNVcyWkpVTk9YcHBjT1lFK2xvUW5rbFdjYzAwekdONHhMU1hMbFBoWFV0bXBra2FuQ1dzUWVMYWoyRUJoU3huRFhpZnVEVkscHBjT1l1FK2xvUW5rb5FERBNVcyWkpVTk9YcHBjT1lFK2xvUW5rbFdjYzAwekdONHhMU1hMbFBoWFV0bXBra2FuQ1dzUWVMYWoyRUJoUhuRFhpZnVEyZE9WNGJtQUhMM2lSZ1JWXVzWldKaUROeThadVONVVNUlJ3N3NFVFJZMwkpVTk9YcHBjT1lF2xvUW5rbFdjYzAwekdONHhMU1hMbFBoWFV0bXBra2FuQ1dzUWVMYWoyRUJS2dBOU9Z4cHBjT1lFK2xvUW5rbFdjYzAwekdONHhMU1hMbFBoWFV0bXBra772Fu1dzUWVMYWoyRUJS2dBOUZ4NExhaERBNVcykpVTk9YcHBjT1lFK2xvUW5rbFdjYzAwekdONHhMU1hMbFBoWFV0bXBra2FuQ1dzUWVMYWoyRUJoUhuRFhpZnVENExhaERBNVcyWkpVTk9YcHBjT1lFK2xvUW5rbFdjYzAwekdONHhMU1hMbFBoWFV0bXBra2FuQ1dzUWVMYWoyRUJU3huRFhpZnVEVkscHBjT1lFK2xvUW5rbFdjYzAwekdONHhMU1hMbFBoWFV0bXBra2FuQ1dUWVMYWoyRUJS2dBOUZ4NExhaERBNVcyWkpVTk9YcHBjT1lFK2xvUW5rbFdjYzAwekdONHhMU1hMbFBoWFV0bXBra2FuQ1dzUWVMYWoyRUJoU3huRFhpZnVEyZE9WNGJtQUhMM2lSZ1J0WXVzWldKaUROeThadTVONVVNUlJ3N3NFVFJZM2w_.pdf”
\n","event":[{"listen":"prerequest","script":{"type":"text/javascript","exec":[""],"id":"28745138-118b-4708-8042-f76c4fff6c24"}},{"listen":"test","script":{"type":"text/javascript","exec":[""],"id":"1ff64bd0-fa4c-4fd0-8982-92b691f9d7fa"}}],"_postman_id":"a3b0d97b-66fb-4cb8-8ea3-97c6fa717b7e"}],"event":[{"listen":"prerequest","script":{"type":"text/javascript","exec":[""],"id":"2ba12206-f089-4984-9b4e-715c5933548d"}},{"listen":"test","script":{"type":"text/javascript","exec":[""],"id":"551e931b-ce3a-49cb-bba5-bcb0a7531589"}}]}