![\"https://developer.japer.io\"](\"https://i.imgur.com/SH6Qrzb.jpg\")
https://developer.japer.ioThis JAPER API leverages AWS to deliver service status, device management, customer validation, data encryption and decryption. It integrates seamlessly with our JAPER iOS and Android apps to deliver JAPER Outcome as a globally scalable, latency-minimized, end-to-end encrypted infrastructure, documented and seamless to integrate.
\nJust getting started? Explore Developer Quickstart. Need help? Visit Developer Support. Not a developer? Level up with coding.
\n","schema":"https://schema.getpostman.com/json/collection/v2.0.0/collection.json","toc":[],"owner":"5724568","collectionId":"7c155253-a731-4b59-9789-fa841ae9f489","publishedId":"S1Zw8qoK","public":true,"customColor":{"top-bar":"FFFFFF","right-sidebar":"20082A","highlight":"AC43D9"},"publishDate":"2020-05-29T00:55:05.000Z"},"item":[{"name":"Japer Technology Pty. Ltd.","item":[{"name":"JAPER API Documentation","item":[],"id":"1f4a405f-9cca-491b-be65-1fd48d5e39d5","description":"In this API Documentation, you will encounter URL formatted as BOLDED-CAPITAL-LETTERS-WITH-MINUS-SIGNS. These are JAPER App Deep Links. On a smart device with the JAPER App installed, tapping them launches the app directly. Otherwise, they generate a barcode for manual scanning by a JAPER App.
\nIf you’re viewing this API documentation on a device that can’t run the JAPER App, scan the QR code with a supported smart device for the best documentation experience.
\n
The JAPER App is a lightweight client application that provides secure, interactive functionality by interpreting data from the JAPER API. It requires only internet and camera access on your smart device.
\nPlease ensure that the JAPER iOS App or the JAPER Android App is installed and operational for optimal documentation use and understanding.
\nIn 2017 JAPER-TECHNOLOGY was founded by ERIC-MOURANT and GARRY-PEARSON-OAM, we developed the JAPER-API and the closely integrated JAPER-APP. This JAPER-MECHANISM has enabled the creation of JAPER-NAMESPACE, JAPER-DATASPACE, and JAPER-KEYSPACE.
\n![\"JAPER-HELLO-WORLD\"](\"https://i.imgur.com/SZh4HcO.png\")
The JAPER-HELLO-WORLD is a minimum definition that showcases JAPER-OUTCOME to display \"Hello, World!\" using the JAPER App.
\nThis is the OpenAPI v3.1 definition of the JAPER Outcome JSON Schema
\n","_postman_id":"1f4a405f-9cca-491b-be65-1fd48d5e39d5","auth":{"type":"noauth","isInherited":true,"source":{"_postman_id":"cd74a3ae-394c-4dbb-8af6-5951509aa55c","id":"cd74a3ae-394c-4dbb-8af6-5951509aa55c","name":"Japer Technology Pty. Ltd.","type":"folder"}}},{"name":"Quick Index","item":[],"id":"8326d4ce-1603-43e4-8bbe-a4e29206e8ad","description":"","_postman_id":"8326d4ce-1603-43e4-8bbe-a4e29206e8ad","auth":{"type":"noauth","isInherited":true,"source":{"_postman_id":"cd74a3ae-394c-4dbb-8af6-5951509aa55c","id":"cd74a3ae-394c-4dbb-8af6-5951509aa55c","name":"Japer Technology Pty. Ltd.","type":"folder"}}},{"name":"JAPER@Postman","item":[],"id":"83152960-1b3c-4da2-8598-12515036c801","description":"For detailed API insights into the JAPER Ecosystem, please consult our Public JAPER API Workspace on the Postman API Network. This provides JAPER Developers with the tools to integrate the JAPER API into their applications. The JAPER GPT can answer questions about Postman.
\n![\"https://www.postman.com/japer-technology/japer-public-workspace/collection/wwow3o3/japer-api\"](\"https://run.pstmn.io/button.svg\")
\n\n","auth":{"type":"noauth","isInherited":false},"event":[{"listen":"prerequest","script":{"id":"173fb33b-51b4-4d8c-8b51-1e8e2e38be13","type":"text/javascript","packages":{},"exec":[""]}},{"listen":"test","script":{"id":"0eee7802-1b4a-4222-8937-cd6346a5fb0d","type":"text/javascript","packages":{},"exec":[""]}}],"_postman_id":"83152960-1b3c-4da2-8598-12515036c801"},{"name":"JAPER@OpenAI","item":[],"id":"94f0ff11-e996-4d8b-a0c5-12dc7cc5cfa3","description":"Download the free Postman Application, click the
\nRun in Postmanbutton (above), make sure to select theJAPER APIenvironment on the top right, add your JAPER API Key and IDs to the environment variables.
For detailed AI insights into the JAPER Ecosystem, please consult our JAPER Technology OpenAI Custom ChatGPT.
\n![\"https://chat.openai.com/g/g-GrNiWW5CX-JAPER-Technology-Pty-Ltd\"](\"https://i.imgur.com/As0hEpj.jpg\")
\n\n","auth":{"type":"noauth","isInherited":false},"event":[{"listen":"prerequest","script":{"id":"1bf1ad78-a621-4481-ab45-588bad93d32b","type":"text/javascript","packages":{},"exec":[""]}},{"listen":"test","script":{"id":"5c532f16-6e3d-438c-ac5f-fbdce7230898","type":"text/javascript","packages":{},"exec":[""]}}],"_postman_id":"94f0ff11-e996-4d8b-a0c5-12dc7cc5cfa3"},{"name":"JAPER@GitHub","item":[],"id":"de9f8fa1-ddf2-45ee-9199-481d660ef9fd","description":"Our JAPER GPT is a precognitive repository of JAPER knowledge, designed to deliver precise and context-aware answers by leveraging curated information about the JAPER ecosystem.
\n
For detailed source-coded insights into the JAPER Ecosystem, please consult our JAPER Technology GitHub Repository.
\n
\n\n","auth":{"type":"noauth","isInherited":false},"event":[{"listen":"prerequest","script":{"id":"1bf1ad78-a621-4481-ab45-588bad93d32b","type":"text/javascript","packages":{},"exec":[""]}},{"listen":"test","script":{"id":"5c532f16-6e3d-438c-ac5f-fbdce7230898","type":"text/javascript","packages":{},"exec":[""]}}],"_postman_id":"de9f8fa1-ddf2-45ee-9199-481d660ef9fd"},{"name":"JAPER API Summary","item":[],"id":"1da14574-5b87-40c4-9522-50aacc078584","description":"The JAPER GitHub repository is the authoritative hub for all JAPER knowledge—offering meticulously curated code, documentation, and examples to support precise, context-aware development across the entire ecosystem.
\n
/ping
Check the status of JAPER AWS API Gateway.
/v1/ping
Check the status of JAPER AWS Lambda.
/v1/x/nexus/status
Check the status of JAPER Nexus.
/v1/x/device/create
Create a new JAPER Device.
/v1/x/device/status
Retrieve the status of a JAPER Device.
/v1/x/device/purge
Remove all validations from a JAPER Device.
/v1/x/device/kill
Permanently disable a JAPER Device.
/v1/x/encrypt
Encrypt data to generate JAPER Data
/v1/x/decrypt
Decrypt JAPER Data (aliases: lookup, execute).
/v1/x/validation/attempt
Conduct PIN validation from email or sms.
/v1/x/validate/domain
Conduct domain validation via DNS TXT record.
/v1/x/validate/email
Send a validation email PIN.
/v1/x/validate/sms
Dispatch a validation SMS PIN.
/v1/x/validation/status
Check a JAPER Customer's opt-out status.
An Australian Company
ABN 44614214863
DUNS 744400810
![\"https://www.japer.technology\"](\"https://s3-ap-southeast-2.amazonaws.com/about.japer.cloud/Japer-300x256.gif\")
![](\"https://s3-ap-southeast-2.amazonaws.com/about.japer.cloud/JAPER-Black-Name-192x37.gif\")
\n\nThis is the only unauthenticated endpoint and confirms the JAPER API is defined and reachable via the AWS API Gateway.
\n
200 = OK
healthy
\nAustralia
api.japer[.io|.services|.systems|-ap-southeast-2.net]
Germany
api.japer-eu-central-1.net
Japan
api.japer-ap-northeast-1.net
Singapore
api.japer-ap-southeast-1.net
UK
api.japer-eu-west-2.net
JAPER-URL[site]api.japer.io/ping
\n![\"https://api.japer.io/ping\"](\"https://i.imgur.com/8RYafMb.png\")
\n\nThis API endpoint triggers an AWS Lambda function to confirm Lambda is operational.
\n
200 = OK
healthy
\n
\n\nThis API endpoint triggers a JAPER AWS Lambda function to confirm the JAPER Nexus is operational.
\n
200 = Ping is OK
JAPER@{JAPER API Entry Point Domain}@{AWS Region}::NEXUS healthy
ping@japer.services returns an email to the sender.
\nstatus@japer.services returns an email received trust analysis to the sender.
\n![\"JAPER-PING\"](\"https://i.imgur.com/k6YAqnV.png\")
These diagnostic and operational commands within the JAPER Ecosystem are used to verify the availability and status of JAPER Technology digital resources. They serve as a lightweight mechanism to assess JAPER's operational readiness.
\nThree levels:
\n/ping
Tests the availability of a JAPER AWS API Gateway endpoint.
/v1/ping
Tests JAPER AWS Lambda integration through the API Gateway.
/v1/x/nexus/status
Tests whether the JAPER-NEXUS-STATUS is operational.
\n\nCreates a new device and returns a new
\nJAPER Device ID.
201 = Device ID created.
{{JAPER Device ID}}
\n","urlObject":{"path":["create"],"host":["https://api.japer.io/v1/x/device"],"query":[],"variable":[]}},"response":[{"id":"560576a2-4e5e-445b-b819-6cc2e46ec159","name":"create","originalRequest":{"method":"PUT","header":[{"key":"japer-aid","value":"{{JAPER Application ID}}","type":"text"}],"body":{"mode":"raw","raw":""},"url":"https://api.japer.io/v1/x/device/create"},"status":"Created","code":201,"_postman_previewlanguage":"text","header":[],"cookie":[],"responseTime":null,"body":"44characterIDcontainingAlphanumericFullstopsExclamationMarks"}],"_postman_id":"602b2071-0c16-4884-841a-54b170f10934"},{"name":"device/status","event":[{"listen":"test","script":{"id":"2daac955-af26-4e78-8661-803b2e259322","exec":["pm.test(\"Status code is 200\", function () {"," pm.response.to.have.status(200);","});","","pm.test(\"Response time is less than 3 seconds\", function () {"," pm.expect(pm.response.responseTime).to.be.below(3000);","});"],"type":"text/javascript","packages":{}}}],"id":"ff2a70b3-25a4-45a0-8b48-d7db6aa762af","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"auth":{"type":"apikey","apikey":{"basicConfig":[{"key":"key","value":"x-api-key"},{"key":"value","value":"{{JAPER API Key}}"}]},"isInherited":false},"method":"GET","header":[{"key":"japer-aid","value":"{{JAPER Application ID}}","type":"text"},{"key":"japer-did","value":"{{JAPER Device ID}}","type":"text"}],"body":{"mode":"raw","raw":""},"url":"https://api.japer.io/v1/x/device/status","description":"
\n\nReturns JSON information about the device.
\n
200 = Device is known.
204 = Device is unknown.
see: example.
\n![\"JAPER-APP+goto:manage-validations\"](\"https://i.imgur.com/BF281hv.png\")
\n\nPurge device of all validations.
\n
200 = Device was purged.
purged
\n![\"JAPER-APP+goto:purge-validations\"](\"https://i.imgur.com/FB8L0tc.png\")
\n\nThe device is marked as dead to JAPER forever.
\n
200 = Device was killed.
dead
\ndefcon@japer.services looks for a kill code in the subject line of the email.
\n![\"JAPER-APP+goto:disable-app\"](\"https://i.imgur.com/9xJfbCd.png\")
A JAPER Device ID is a 44-character alphanumeric key encoded in JASE64 characters [aZ09.!], ensuring unique, secure identification for encryption, decryption and validation.
\nIf a JAPER Device ID is found in the wild it is automatically disabled.
\n","auth":{"type":"noauth","isInherited":false},"event":[{"listen":"prerequest","script":{"id":"4c202c34-7be2-4cd1-afd7-a2c871b46908","type":"text/javascript","exec":[""]}},{"listen":"test","script":{"id":"f6014cd4-ade3-4af4-a5a1-047f96404168","type":"text/javascript","exec":[""]}}],"_postman_id":"b37162b8-3335-4aa3-b88d-96b8beeff729"},{"name":"Decryptions","item":[{"name":"decrypt","event":[{"listen":"test","script":{"id":"7f1f00b7-5284-4b9e-97bb-1a58cccd0792","exec":["pm.test(\"Status code is 200\", function () {"," pm.response.to.have.status(200);","});","","pm.test(\"Response time is less than 3 seconds\", function () {"," pm.expect(pm.response.responseTime).to.be.below(3000);","});"],"type":"text/javascript","packages":{}}}],"id":"218739dc-adcf-4111-98bf-a6b850a90e4b","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"auth":{"type":"apikey","apikey":{"basicConfig":[{"key":"key","value":"x-api-key"},{"key":"value","value":"{{JAPER API Key}}"}]},"isInherited":false},"method":"POST","header":[{"key":"japer-aid","value":"{{JAPER Application ID}}","type":"text"},{"key":"japer-did","value":"{{JAPER Device ID}}","type":"text"},{"key":"japer-data","value":"{{JAPER Command}}","type":"text"}],"body":{"mode":"raw","raw":""},"url":"https://api.japer.io/v1/x/decrypt","description":"
200 = JAPER
204 = Not JAPER
see: JAPER Outcome
\n","urlObject":{"host":["https://api.japer.io/v1/x/decrypt"],"query":[],"variable":[]}},"response":[{"id":"a8402f45-d8de-4e39-9b31-e8baf5956f6b","name":"decrypt","originalRequest":{"method":"POST","header":[{"key":"japer-aid","value":"{{JAPER Application ID}}","type":"text"},{"key":"japer-did","value":"{{JAPER Device ID}}","type":"text"},{"key":"japer-data","value":"{{JAPER Command}}","type":"text"}],"body":{"mode":"raw","raw":""},"url":"https://api.japer.io/v1/x/decrypt"},"_postman_previewlanguage":null,"header":null,"cookie":[],"responseTime":null,"body":null}],"_postman_id":"218739dc-adcf-4111-98bf-a6b850a90e4b"},{"name":"lookup","event":[{"listen":"test","script":{"id":"ac474f4a-606a-41f9-8e46-7bf8929fafa9","exec":["pm.test(\"Status code is 200\", function () {"," pm.response.to.have.status(200);","});","","pm.test(\"Response time is less than 3 seconds\", function () {"," pm.expect(pm.response.responseTime).to.be.below(3000);","});"],"type":"text/javascript","packages":{}}}],"id":"e38e344b-ca93-41a9-992c-5647dcb78fbd","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"auth":{"type":"apikey","apikey":{"basicConfig":[{"key":"key","value":"x-api-key"},{"key":"value","value":"{{JAPER API Key}}"}]},"isInherited":false},"method":"POST","header":[{"key":"japer-aid","value":"{{JAPER Application ID}}","type":"text"},{"key":"japer-did","value":"{{JAPER Device ID}}","type":"text"},{"key":"japer-data","value":"{{JAPER Command}}","type":"text"}],"body":{"mode":"raw","raw":""},"url":"https://api.japer.io/v1/x/lookup","description":"
200 = JAPER
204 = Not JAPER
see: JAPER Outcome JSON Schema
\nhttps://www.japer.cloud/decrypt
\n","urlObject":{"host":["https://api.japer.io/v1/x/lookup"],"query":[],"variable":[]}},"response":[{"id":"185c6d1d-8559-47fb-8406-5fbfbf9dee5d","name":"lookup","originalRequest":{"method":"POST","header":[{"key":"japer-aid","value":"{{JAPER Application ID}}","type":"text"},{"key":"japer-did","value":"{{JAPER Device ID}}","type":"text"},{"key":"japer-data","value":"{{JAPER Command}}","type":"text"}],"body":{"mode":"raw","raw":""},"url":"https://api.japer.io/v1/x/lookup"},"_postman_previewlanguage":null,"header":null,"cookie":[],"responseTime":null,"body":null}],"_postman_id":"e38e344b-ca93-41a9-992c-5647dcb78fbd"},{"name":"execute","event":[{"listen":"test","script":{"id":"ac474f4a-606a-41f9-8e46-7bf8929fafa9","exec":["pm.test(\"Status code is 200\", function () {"," pm.response.to.have.status(200);","});","","pm.test(\"Response time is less than 3 seconds\", function () {"," pm.expect(pm.response.responseTime).to.be.below(3000);","});"],"type":"text/javascript","packages":{}}}],"id":"f8f0f1d2-f8c9-4284-b641-b680ce64cfd4","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"auth":{"type":"apikey","apikey":{"basicConfig":[{"key":"key","value":"x-api-key"},{"key":"value","value":"{{JAPER API Key}}"}]},"isInherited":false},"method":"POST","header":[{"key":"japer-aid","value":"{{JAPER Application ID}}"},{"key":"japer-did","value":"{{JAPER Device ID}}"},{"key":"japer-data","value":"{{JAPER Command}}"}],"body":{"mode":"raw","raw":""},"url":"https://api.japer.io/v1/x/execute","description":"
200 = JAPER
204 = Not JAPER
The decrypt, lookup, and execute functions are interchangeable aliases for a unified core operation, each tailored to emphasize a specific technical context: decrypt for secure processing of encrypted commands, lookup for data retrieval, and execute for direct command execution. This design provides semantic flexibility, allowing developers to interact with the API in a way that aligns with their application needs while maintaining consistent processing of JAPER Namespace commands into structured JAPER Outcome JSON Schema.
These functions abstract complex operations over JAPER Dataspace, Namespace, and Keyspace, leveraging dynamic processing to decipher commands, interpret parameters, and trigger workflows. The architecture remains extensible, supporting the seamless addition of new namespaces and parameters without increasing API complexity.
\nThe data variable for the decrypt, lookup, or execute functions can be determined by a path parameter, /v1/x/lookup/9300650018860, These methods allow JAPER Namespace commands to be passed directly in the URL but is overridden if data is provided other another method, such as the request body or query parameters.
https://www.japer.cloud/decrypt
\n\n","auth":{"type":"noauth","isInherited":false},"event":[{"listen":"prerequest","script":{"id":"2514c258-6ef3-4e4a-8b63-1c045bc894a4","type":"text/javascript","exec":[""]}},{"listen":"test","script":{"id":"9a84dec8-773c-4257-b104-60a0aacfa02f","type":"text/javascript","exec":[""]}}],"_postman_id":"f682cbc2-3e69-4586-b759-a61d3b5e5cbe"},{"name":"Encryptions","item":[{"name":"encrypt","event":[{"listen":"test","script":{"id":"c86c1860-5ad3-4c79-9efd-d3740d767106","exec":[""],"type":"text/javascript","packages":{}}},{"listen":"prerequest","script":{"id":"d853ea88-9b1d-4196-8f7a-f50613e86071","exec":["const body = {\r"," \"outcome\":{\r"," \"cache\":3600,\r"," \"type\":\"JAPER\",\r"," \"lookup\":\"ERIC\",\r"," \"data\":[\r"," {\"draw\":\"ar\",\"order\":1,\"size\":-4,\"type\":\"text\",\"value\":\"Eric Mourant\",\"justify\":\"middle\"},\r"," {\"draw\":\"full\",\"order\":2,\"size\":0,\"type\":\"text\",\"value\":\"Eric Mourant\",\"justify\":\"middle\"},\r"," {\"draw\":\"full\",\"order\":3,\"type\":\"text\",\"size\":-12,\"value\":\" \",\"justify\":\"middle\"},\r"," {\"draw\":\"full\",\"order\":4,\"type\":\"text\",\"size\":-6,\"value\":\"CEO and Co-Founder\",\"justify\":\"middle\"},\r"," {\"draw\":\"full\",\"order\":5,\"type\":\"text\",\"size\":-8,\"value\":\"Japer Technology Pty. Ltd.\",\"justify\":\"middle\"}\r"," {\"draw\":\"full\",\"order\":5,\"type\":\"text\",\"size\":-8,\"value\":\"+61 0 412 646 711 \",\"justify\":\"middle\"}\r"," ]\r"," }\r","};\r","\r","pm.globals.set(\"body\", JSON.stringify(body));"],"type":"text/javascript","packages":{}}}],"id":"bd5a0746-7e44-444b-bafc-e092762fb577","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"auth":{"type":"apikey","apikey":{"basicConfig":[{"key":"key","value":"x-api-key"},{"key":"value","value":"{{JAPER API Key}}"}]},"isInherited":false},"method":"POST","header":[{"key":"japer-aid","value":"{{JAPER Application ID}}","type":"text"},{"key":"japer-cid","value":"{{JAPER Customer ID}}","type":"text"},{"key":"japer-did","value":"{{JAPER Device ID}}","type":"text"},{"key":"japer-target","value":"{{JAPER Customers}}","type":"text"},{"key":"japer-data","value":"{{JAPER Command}}","type":"text"}],"body":{"mode":"raw","raw":"{\r\n \"japer\": {\r\n \"outcome\" : { \r\n \"$ref\": \"https://www.japer.tools/json-schema/outcome.json\" \r\n }\r\n }\r\n}","options":{"raw":{"language":"json"}}},"url":"https://api.japer.io/v1/x/encrypt","description":"
\n\n","urlObject":{"host":["https://api.japer.io/v1/x/encrypt"],"query":[],"variable":[]}},"response":[{"id":"86f56a29-b404-42b0-ae68-10d7e36b125b","name":"JAPER-DATASPACE","originalRequest":{"method":"POST","header":[{"key":"japer-aid","value":"{{JAPER Application ID}}","type":"text"},{"key":"japer-cid","value":"{{JAPER Customer ID}}","type":"text"},{"key":"japer-did","value":"{{JAPER Device ID}}","type":"text"},{"key":"japer-target","value":"eric.mourant@japer.technology","type":"text"},{"key":"japer-data","value":"JAPER-DATASPACE","type":"text"}],"body":{"mode":"raw","raw":"{\r\n \"japer\": {\r\n \"outcome\" : { \r\n \"$ref\": \"https://www.japer.tools/json-schema/outcome.json\" \r\n }\r\n }\r\n}","options":{"raw":{"language":"json"}}},"url":"https://api.japer.io/v1/x/encrypt"},"_postman_previewlanguage":"json","header":[{"key":"Content-Type","value":"application/json","description":"","type":"text"}],"cookie":[],"responseTime":null,"body":"{\r\n {\r\n \"japer\": {\r\n \"command\": \"JAPER-KEYSPACE\",\r\n \"key\": \"ERIC-MOURANT-XYZ://Example\"\r\n },\r\n \"outcome\": {\r\n \"cache\": 600,\r\n \"type\": \"JAPER\",\r\n \"full_title_1\": \"Hello\",\r\n \"full_title_2\": \"Eric\",\r\n \"full_hide_all_buttons\": \"yes\",\r\n \"data\": [\r\n {\r\n \"draw\": \"all\",\r\n \"order\": 1,\r\n \"type\": \"text\",\r\n \"value\": \"This Hello resides in JAPER-KEYSPACE, between customers and a key.\"\r\n }\r\n ]\r\n }\r\n}"},{"id":"27d0f4de-7cf7-4774-8ba5-acaa53b98505","name":"JAPER-KEYSPACE","originalRequest":{"method":"POST","header":[{"key":"japer-aid","value":"{{JAPER Application ID}}","type":"text"},{"key":"japer-cid","value":"{{JAPER Customer ID}}","type":"text"},{"key":"japer-did","value":"{{JAPER Device ID}}","type":"text"},{"key":"japer-target","value":"eric.mourant@japer.technology","type":"text"},{"key":"japer-data","value":"","type":"text"}],"body":{"mode":"raw","raw":"{\r\n \"japer\": {\r\n \"outcome\" : { \r\n \"$ref\": \"https://www.japer.tools/json-schema/outcome.json\" \r\n }\r\n }\r\n}","options":{"raw":{"language":"json"}}},"url":"https://api.japer.io/v1/x/encrypt"},"_postman_previewlanguage":"json","header":[{"key":"Content-Type","value":"application/json","description":"","type":"text"}],"cookie":[],"responseTime":null,"body":"{\n {\n \"japer\": {\n \"command\": \"JAPER-KEYSPACE\",\n \"key\": \"ERIC-MOURANT-XYZ://Example\"\n },\n \"outcome\": {\n \"cache\": 600,\n \"type\": \"JAPER\",\n \"full_title_1\": \"Hello\",\n \"full_title_2\": \"Eric\",\n \"full_hide_all_buttons\": \"yes\",\n \"data\": [\n {\n \"draw\": \"all\",\n \"order\": 1,\n \"type\": \"text\",\n \"value\": \"This Hello resides in JAPER-KEYSPACE, between customers and a key.\"\n }\n ]\n }\n}"}],"_postman_id":"bd5a0746-7e44-444b-bafc-e092762fb577"}],"id":"d24e3a9e-d43e-426f-bce7-1b84a71ab5ac","description":"Encrypts outcome between customers.
\n
This JAPER Outcome JSON Schema, https://www.japer.tools/json-schema/outcome.json, is strictly enforced during JAPER Encryption.
\nThis core business function of JAPER provides allows JAPER Outcome at the intersection of a barcode, a business domain and a business customer email address, mobile telephone or internet domain.
\nAn encryption is processed as the decryption of a encryption command.
\n","auth":{"type":"noauth","isInherited":false},"event":[{"listen":"prerequest","script":{"id":"1103c37a-0940-47cc-9124-b8da9ca7def0","type":"text/javascript","exec":[""]}},{"listen":"test","script":{"id":"b024f33e-5afe-4c62-8052-b006323a3a1a","type":"text/javascript","exec":[""]}}],"_postman_id":"d24e3a9e-d43e-426f-bce7-1b84a71ab5ac"},{"name":"Validations","item":[{"name":"validation/attempt","event":[{"listen":"test","script":{"id":"8443343b-8fe9-4d26-a4f0-de71f1006ea5","exec":["pm.test(\"Status code is 200\", function () {"," pm.response.to.have.status(200);","});","","pm.test(\"Response time is less than 3 seconds\", function () {"," pm.expect(pm.response.responseTime).to.be.below(3000);","});"],"type":"text/javascript","packages":{}}}],"id":"1bd10f4b-10bc-4471-a2bb-a59fcbe2d657","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"auth":{"type":"apikey","apikey":{"basicConfig":[{"key":"key","value":"x-api-key"},{"key":"value","value":"{{JAPER API Key}}"}]},"isInherited":false},"method":"PUT","header":[{"key":"japer-aid","value":"{{JAPER Application ID}}","type":"text"},{"key":"japer-did","value":"{{JAPER Device ID}}","type":"text"},{"key":"japer-gocode","value":"{{JAPER Validation Code}}","type":"text"}],"body":{"mode":"raw","raw":""},"url":"https://api.japer.io/v1/x/validate/attempt","description":"
\n\nThis JAPER 6-digit PIN validation API endpoint verifies user-entered codes for email or SMS, ensuring secure access and authentication.
\n
200 = Validation attempt failed.
201 = Validation is successful and a Device Customer Validation has been created.
200 = fail
201 = validated
![\"JAPER-APP+goto:enter-validation-code\"](\"https://i.imgur.com/ulC0T8L.png\")
Mandatory: RFC 1035, Section 2.3.1 defines domain names as alphanumeric labels, 63 characters max, separated by dots, case-insensitive.
\n","type":"text"}],"body":{"mode":"raw","raw":""},"url":"https://api.japer.io/v1/x/validate/domain","description":"
\n\nSearches the DNS for an encoded TXT and messages the outcome to the parent email address.
\n
201 = DNS TXT Definition found and Validation created.
Mandatory: RFC 5322, Section 3.4.1 defines email address syntax as local-part@domain, with strict rules for valid characters and structure.
\n","type":"text"}],"body":{"mode":"raw","raw":""},"url":"https://api.japer.io/v1/x/validate/device/email","description":"
\n\nIssues a one-time PIN challenge for device–email binding and sends the PIN by email.
\n
201 = Email sent and Validation created.
![\"JAPER-APP+goto:validate-email\"](\"https://i.imgur.com/dmwQjk3.png\")
E.164 format: +[Country Code][Subscriber Number], max 15 digits.
\n","type":"text"}],"body":{"mode":"raw","raw":""},"url":"https://api.japer.io/v1/x/validate/device/sms","description":"
\n\nIssues a one-time PIN challenge for device–mobile binding and sends the PIN by SMS when applicable.
\n
201 = SMS sent and Validation created.
202 = SMS not sent because zero data exists.
201 = sms
202 = fail
![\"JAPER-APP+goto-validate-sms\"](\"https://i.imgur.com/w6KtH1c.png\")
\n\nReturns information about a customer. The information is shaped by the validations association with the did.
\n
200 = Customer is known
201 = Customer is known and has opted in
202 = Customer is known and has opted out
204 = Customer is unknown
JAPER offers secure validation of email, SMS, and domain data via robust API endpoints, integrating DNS requirements and verification codes to ensure comprehensive and reliable authentication.
\nIf a JAPER Validation ID is found in the wild it is automatically disabled.
\n","auth":{"type":"noauth","isInherited":false},"event":[{"listen":"prerequest","script":{"id":"e58d0512-1a68-45bf-bdbf-671a1599c796","type":"text/javascript","exec":[""]}},{"listen":"test","script":{"id":"b4460c3f-7c7e-458b-9149-2d2d4e7dc3f3","type":"text/javascript","exec":[""]}}],"_postman_id":"25c88192-276f-4e2c-bc79-489a391f6e58"},{"name":"Developer Quickstart","item":[{"name":"1. Download App","item":[],"id":"86794cea-bcee-4037-b0cd-ee5a360f647c","description":"Every JAPER Developer should download the JAPER App to test, validate, and interact with JAPER APIs, feel the seamlessness, touch real-time execution of JAPER Namespace and direct interaction with JAPER Outcomes.
\nAfter installation, open the JAPER App and tap the JAPER logo (top right) to access the Main Menu; tap again to close it. This menu provides access to information, customer validation, barcode lookup, and namespace execution, allowing users to explore applications, check device and customer status, and interact with JAPER Outcomes.
\n\n\nIf you know JAPER and know yourself, you need not fear the Outcome of JAPER.
\n
PDF: JAPER App User Manual
\n","_postman_id":"86794cea-bcee-4037-b0cd-ee5a360f647c","auth":{"type":"noauth","isInherited":true,"source":{"_postman_id":"129153ca-70e7-4114-a276-aefa10e76cfd","id":"129153ca-70e7-4114-a276-aefa10e76cfd","name":"Developer Quickstart","type":"folder"}}},{"name":"2. Validate Email","item":[],"id":"52e841f4-327e-45cb-b489-94a281148552","description":"A JAPER Developer should validate an email address to become a JAPER Email Customer, enabling secure access to JAPER resources, permissions-driven operations, and integration with JAPER APIs for encrypted data management.
\n\n\n\nWe must be able to communicate.
\n
PDF: JAPER Email Customer Manual
\n","_postman_id":"52e841f4-327e-45cb-b489-94a281148552","auth":{"type":"noauth","isInherited":true,"source":{"_postman_id":"129153ca-70e7-4114-a276-aefa10e76cfd","id":"129153ca-70e7-4114-a276-aefa10e76cfd","name":"Developer Quickstart","type":"folder"}}},{"name":"3. Validate Email Domain","item":[],"id":"458a149c-89a9-4288-8930-aa9d0ca72b99","description":"A JAPER Developer should validate a domain and become a JAPER Domain Customer to securely link their domain to JAPER services, enabling trusted namespace ownership, enhanced resource control, and streamlined access to domain-specific JAPER Outcomes.
\n\n\n\nTruth requires proof and declaration.
\n
PDF: JAPER Domain Customer Manual
\n","_postman_id":"458a149c-89a9-4288-8930-aa9d0ca72b99","auth":{"type":"noauth","isInherited":true,"source":{"_postman_id":"129153ca-70e7-4114-a276-aefa10e76cfd","id":"129153ca-70e7-4114-a276-aefa10e76cfd","name":"Developer Quickstart","type":"folder"}}},{"name":"4. Explore Namespace","item":[],"id":"e30ce8fa-821e-4292-9cdd-74b0c008566b","description":"A JAPER Developer should review the JAPER Namespace overview to understand its structured command framework, enabling precise implementation of JAPER APIs, resource management, and seamless integration across the JAPER Ecosystem.
\n\n\n\nIn the midst of JAPER, there is opportunity.
\n
PDF: JAPER Namespace Manual
\n","_postman_id":"e30ce8fa-821e-4292-9cdd-74b0c008566b","auth":{"type":"noauth","isInherited":true,"source":{"_postman_id":"129153ca-70e7-4114-a276-aefa10e76cfd","id":"129153ca-70e7-4114-a276-aefa10e76cfd","name":"Developer Quickstart","type":"folder"}}},{"name":"5. Explore Email Services","item":[],"id":"fb09cc6d-fe78-437d-b147-15d61d5c579e","description":"JAPER Developers should explore JAPER Email Services to drive the JAPER API via email, enabling automated, human-friendly workflows for executing commands, triggering validations, and managing resources without using API calls. This approach ensures seamless integration into existing email systems while supporting asynchronous operations.
\n\n\nClear orders delivered swiftly turn clarity into reality.
\n
PDF: JAPER Email Customer Manual
\n","_postman_id":"fb09cc6d-fe78-437d-b147-15d61d5c579e","auth":{"type":"noauth","isInherited":true,"source":{"_postman_id":"129153ca-70e7-4114-a276-aefa10e76cfd","id":"129153ca-70e7-4114-a276-aefa10e76cfd","name":"Developer Quickstart","type":"folder"}}},{"name":"6. Explore Keyspace","item":[],"id":"87db7d21-821c-4a00-bb97-8fee670f4c8d","description":"A JAPER Developer should explore JAPER Keyspace to manage encrypted data securely, leverage hierarchical access control, and enable precise, permissions-driven interactions that link creators, customers, and resources within the JAPER Ecosystem.
\n\n\n\nControl the path, and the destination is certain.
\n
PDF: JAPER Customer Keyspace Manual
\n","_postman_id":"87db7d21-821c-4a00-bb97-8fee670f4c8d","auth":{"type":"noauth","isInherited":true,"source":{"_postman_id":"129153ca-70e7-4114-a276-aefa10e76cfd","id":"129153ca-70e7-4114-a276-aefa10e76cfd","name":"Developer Quickstart","type":"folder"}}},{"name":"7. Validate Webhook","item":[],"id":"69de0054-a2fa-4b3d-81a1-a0b371e1a028","description":"A JAPER Developer should validate webhooks to ensure secure, accurate communication both into and out of the system. This prevents unauthorized access, data tampering, and ensures reliable event handling within the JAPER Ecosystem.
\n\n\n\nImmutable signals, swift action, precise outcomes.
\n
PDF: JAPER Customer Webhook Manual
\n","_postman_id":"69de0054-a2fa-4b3d-81a1-a0b371e1a028","auth":{"type":"noauth","isInherited":true,"source":{"_postman_id":"129153ca-70e7-4114-a276-aefa10e76cfd","id":"129153ca-70e7-4114-a276-aefa10e76cfd","name":"Developer Quickstart","type":"folder"}}},{"name":"8. Obtain API Credentials","item":[],"id":"5a619889-07af-49cd-9561-88ef53f541c1","description":"We sell credentials to access to our JAPER API:
\nLogin to the www.japer.technology website.
\nPurchase the credentials you need at the JAPER Technology Shop.
\n\n\nRewards for good security should not be deferred a single day.
\n
PDF: JAPER API Programming Manual
\n","_postman_id":"5a619889-07af-49cd-9561-88ef53f541c1","auth":{"type":"noauth","isInherited":true,"source":{"_postman_id":"129153ca-70e7-4114-a276-aefa10e76cfd","id":"129153ca-70e7-4114-a276-aefa10e76cfd","name":"Developer Quickstart","type":"folder"}}},{"name":"9. Download Postman","item":[],"id":"3cd9c1b8-ebd6-41aa-812f-79c9bf7c50a7","description":"Downloading Postman for JAPER API R&D is essential for streamlining development and testing processes. With Postman, you can efficiently test JAPER’s APIs, simulate API requests, debug responses, and explore endpoints interactively. It simplifies experimentation, accelerates integration, and ensures your JAPER-powered applications meet performance and security standards.
\n\n\n\nOpportunities multiply as they are posted.
\n
PDF: JAPER@Postman Manual
\n","_postman_id":"3cd9c1b8-ebd6-41aa-812f-79c9bf7c50a7","auth":{"type":"noauth","isInherited":true,"source":{"_postman_id":"129153ca-70e7-4114-a276-aefa10e76cfd","id":"129153ca-70e7-4114-a276-aefa10e76cfd","name":"Developer Quickstart","type":"folder"}}},{"name":"10. First API Request","item":[],"id":"0e6f7f5e-9c21-481d-b421-e5dcd683c85e","description":"To make your first API call to the JAPER API, start by installing and launching a API development and testing tool of your choice.
\nCreate a new request and select the appropriate HTTP method, GET.
\nEnter the API endpoint URL, such as https://api.japer.systems/x/ping, in the request field.
Navigate to the Headers section and add the required credential, x-api-key, to authenticate the request.
\nOnce everything is set up, click Send to execute the request.
\nCheck the API response to verifying the connection and configuration success.
\n\n\nVictorious programmers win first then go to war with right tool.
\n
PDF: JAPER API Developer's Manual
\n","_postman_id":"0e6f7f5e-9c21-481d-b421-e5dcd683c85e","auth":{"type":"noauth","isInherited":true,"source":{"_postman_id":"129153ca-70e7-4114-a276-aefa10e76cfd","id":"129153ca-70e7-4114-a276-aefa10e76cfd","name":"Developer Quickstart","type":"folder"}}},{"name":"11. Iterate JAPER","item":[],"id":"a9c41ce7-a3cb-45ff-b3cb-ed706440ed42","description":"The JAPER Developer must adopt a mindset focused on secure, structured, and modular solutions:
\nThink Intersectionally
Build solutions at the intersection of creator, validation, and keyspaces for precise control.
Use JAPER Namespaces
Structure commands and data hierarchically for clarity and scalability.
Validate Everything
Integrate JAPER Customer Validation (Email, SMS, DNS) for secure, permission-driven access.
Build Modularity
Use JAPER APIs to create flexible, reusable components.
Test and Iterate
Use the JAPER App to validate workflows and outcomes effectively.
\n\nFrom order comes strength, from strength privacy and security.
\n
PDF: The observable JAPERverse
\n","_postman_id":"a9c41ce7-a3cb-45ff-b3cb-ed706440ed42","auth":{"type":"noauth","isInherited":true,"source":{"_postman_id":"129153ca-70e7-4114-a276-aefa10e76cfd","id":"129153ca-70e7-4114-a276-aefa10e76cfd","name":"Developer Quickstart","type":"folder"}}}],"id":"129153ca-70e7-4114-a276-aefa10e76cfd","description":"
Developer Quickstart => Download App => Validate Email => Validate Domain => Explore Namespace => Explore Email Services => Explore Keyspace => Validate Webhook => Obtain API Credentials => Download Postman => Make Request => Iterate
\n","auth":{"type":"noauth","isInherited":false},"event":[{"listen":"prerequest","script":{"id":"63c225d4-6d45-4c41-83f3-6855deaabaa9","type":"text/javascript","exec":[""]}},{"listen":"test","script":{"id":"221eba70-06d1-46f7-9a6b-a9f4ca503201","type":"text/javascript","exec":[""]}}],"_postman_id":"129153ca-70e7-4114-a276-aefa10e76cfd"},{"name":"Developer Support","item":[{"name":"Table of Contents","item":[],"id":"6ba7eb25-3fe4-46d1-8126-e80bb3b92593","description":"The JAPER API implements three layers of authentication:
\nCredentials: All of our API functions, except one, require a JAPER Technology Pty. Ltd. issued API Key and IDs to allow any access. The JAPER App Developer Kit contains all three components:
\n{{JAPER API Key}} x-api-key is a unique 40 character identifier linking requests to a JAPER Customer. (see: AWS API Gateway Security)
\n{{JAPER Application ID}} AID is a unique cryptographic 44 character identifier linking requests to a specific JAPER Application.
\n{{JAPER Device ID}} DID is a unique cryptographic 44 character identifier linking requests to a specific JAPER Device.
\nEncryption: All communications use HTTPS and AES encryption to protect sensitive data and ensure compliance with privacy standards.
\nAccess Control: Multi-factor validation (email, SMS, domain) and namespaces enforce strict access management and traceability through immutable logs.
\n\n\n","_postman_id":"660d5e61-5005-4ebd-a932-12657f4e6841","auth":{"type":"noauth","isInherited":true,"source":{"_postman_id":"f8ad5e90-03e1-47bb-800d-d96bef4744a9","id":"f8ad5e90-03e1-47bb-800d-d96bef4744a9","name":"Developer Support","type":"folder"}}},{"name":"2. Entry Points","item":[{"name":"x is for Xenodochial","item":[{"name":"x","event":[{"listen":"test","script":{"id":"2175164b-1940-4b1f-99df-56a7aae5d369","exec":["pm.test(\"Status code is 200\", function () {"," pm.response.to.have.status(200);","});","","pm.test(\"Body is correct\", function () {"," pm.expect(pm.response.text()).to.include(\"/healthy.\");","});","","pm.test(\"Response time is less than 2 seconds\", function () {"," pm.expect(pm.response.responseTime).to.be.below(2000);","});"],"type":"text/javascript","packages":{}}}],"id":"f6ac71b9-fd86-40cd-addc-216aed9bf206","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"auth":{"type":"apikey","apikey":{"basicConfig":[{"key":"key","value":"x-api-key"},{"key":"value","value":"{{JAPER API Key}}"}]},"isInherited":false},"method":"GET","header":[],"body":{"mode":"raw","raw":""},"url":"https://api.japer.io/v1/x/nexus/status","description":"All issued JAPER API Keys and JAPER IDs must be encrypted and securely stored, avoiding exposure in code repositories or public platforms. If a credential is detected in an unauthorised location, it is promptly revoked, and the associated customer is also suspended or fined to prevent misuse. JAPER maintains ownership of all Keys and IDs, granting limited usage rights subject to strict monitoring and compliance checks.
\n
GET
\n","urlObject":{"path":["nexus","status"],"host":["https://api.japer.io/v1/x"],"query":[],"variable":[]}},"response":[{"id":"5a9565c5-9b49-442e-87c1-d211a376eac1","name":"x","originalRequest":{"method":"GET","header":[],"body":{"mode":"raw","raw":""},"url":"https://api.japer.io/v1/x/nexus/status"},"status":"OK","code":200,"_postman_previewlanguage":"text","header":[{"key":"Content-Type","value":"text/html"},{"key":"Content-Length","value":"48"},{"key":"Connection","value":"keep-alive"},{"key":"Date","value":"Tue, 26 Nov 2024 07:11:56 GMT"},{"key":"X-Amzn-Trace-Id","value":"Root=1-674574ba-507415b30d4b344e5f69103f;Parent=7fed563b77859e28;Sampled=0;Lineage=1:01f7463b:0"},{"key":"x-amzn-RequestId","value":"7c999df9-1c0f-4c4b-9815-557c44237506"},{"key":"x-amz-apigw-id","value":"B18tJELwSwMEk7Q="},{"key":"X-Cache","value":"Miss from cloudfront"},{"key":"Via","value":"1.1 0cac85989fc39dec91b3deb3364e4378.cloudfront.net (CloudFront)"},{"key":"X-Amz-Cf-Pop","value":"MEL51-P1"},{"key":"X-Amz-Cf-Id","value":"tghV562J2XvP6mp81aI5Q3xrcDCXqL6tPRV4LEU4ufuFmRoNwjCPLQ=="}],"cookie":[],"responseTime":null,"body":"JAPER@api.japer.io@ap-southeast-2::NEXUS healthy"}],"_postman_id":"f6ac71b9-fd86-40cd-addc-216aed9bf206"},{"name":"x","event":[{"listen":"test","script":{"id":"2175164b-1940-4b1f-99df-56a7aae5d369","exec":["pm.test(\"Status code is 200\", function () {"," pm.response.to.have.status(200);","});","","pm.test(\"Body is correct\", function () {"," pm.expect(pm.response.text()).to.include(\"/healthy.\");","});","","pm.test(\"Response time is less than 2 seconds\", function () {"," pm.expect(pm.response.responseTime).to.be.below(2000);","});"],"type":"text/javascript","packages":{}}}],"id":"3799242e-605b-4ae6-b349-a1194febc58a","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"auth":{"type":"apikey","apikey":{"basicConfig":[{"key":"key","value":"x-api-key"},{"key":"value","value":"{{JAPER API Key}}"}]},"isInherited":false},"method":"PUT","header":[],"body":{"mode":"raw","raw":""},"url":"https://api.japer.io/v1/x/nexus/status","description":"PUT
\n","urlObject":{"path":["nexus","status"],"host":["https://api.japer.io/v1/x"],"query":[],"variable":[]}},"response":[{"id":"d288fe98-5055-4fc0-9225-340700ca5735","name":"x","originalRequest":{"method":"PUT","header":[],"body":{"mode":"raw","raw":""},"url":"https://api.japer.io/v1/x/nexus/status"},"status":"OK","code":200,"_postman_previewlanguage":"text","header":[{"key":"Content-Type","value":"text/html"},{"key":"Content-Length","value":"48"},{"key":"Connection","value":"keep-alive"},{"key":"Date","value":"Tue, 26 Nov 2024 07:12:19 GMT"},{"key":"X-Amzn-Trace-Id","value":"Root=1-674574d2-59c30b936b58161c1f562ff6;Parent=6f97da0b236f56e0;Sampled=0;Lineage=1:01f7463b:0"},{"key":"x-amzn-RequestId","value":"d1330fc8-ab6b-4da0-8037-fb4cf402b914"},{"key":"x-amz-apigw-id","value":"B18xAG9SSwMEbng="},{"key":"X-Cache","value":"Miss from cloudfront"},{"key":"Via","value":"1.1 0cac85989fc39dec91b3deb3364e4378.cloudfront.net (CloudFront)"},{"key":"X-Amz-Cf-Pop","value":"MEL51-P1"},{"key":"X-Amz-Cf-Id","value":"-up33zALx1OnBZtyTbRl_3MgX6hmZCF_fgpY14y6yBFaMleDa3U1-A=="}],"cookie":[],"responseTime":null,"body":"JAPER@api.japer.io@ap-southeast-2::NEXUS healthy"}],"_postman_id":"3799242e-605b-4ae6-b349-a1194febc58a"},{"name":"x","event":[{"listen":"test","script":{"id":"2175164b-1940-4b1f-99df-56a7aae5d369","exec":["pm.test(\"Status code is 200\", function () {"," pm.response.to.have.status(200);","});","","pm.test(\"Body is correct\", function () {"," pm.expect(pm.response.text()).to.include(\"/healthy.\");","});","","pm.test(\"Response time is less than 2 seconds\", function () {"," pm.expect(pm.response.responseTime).to.be.below(2000);","});"],"type":"text/javascript","packages":{}}}],"id":"03578f15-f9b7-4ed5-b5b9-8593468475ae","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"auth":{"type":"apikey","apikey":{"basicConfig":[{"key":"key","value":"x-api-key"},{"key":"value","value":"{{JAPER API Key}}"}]},"isInherited":false},"method":"POST","header":[],"body":{"mode":"raw","raw":""},"url":"https://api.japer.io/v1/x/nexus/status","description":"POST
\n","urlObject":{"path":["nexus","status"],"host":["https://api.japer.io/v1/x"],"query":[],"variable":[]}},"response":[{"id":"32f12ce3-9520-4877-b75b-a698b2e6f1f0","name":"x","originalRequest":{"method":"POST","header":[],"body":{"mode":"raw","raw":""},"url":"https://api.japer.io/v1/x/nexus/status"},"status":"OK","code":200,"_postman_previewlanguage":"text","header":[{"key":"Content-Type","value":"text/html"},{"key":"Content-Length","value":"48"},{"key":"Connection","value":"keep-alive"},{"key":"Date","value":"Tue, 26 Nov 2024 07:12:33 GMT"},{"key":"X-Amzn-Trace-Id","value":"Root=1-674574e1-20b5c5a055d6854545c9bb7e;Parent=669420fdddb1a5ef;Sampled=0;Lineage=1:01f7463b:0"},{"key":"x-amzn-RequestId","value":"5640a273-3a25-4d4f-a647-0524d6b6c6cb"},{"key":"x-amz-apigw-id","value":"B18zPHLkywMEZGg="},{"key":"X-Cache","value":"Miss from cloudfront"},{"key":"Via","value":"1.1 0cac85989fc39dec91b3deb3364e4378.cloudfront.net (CloudFront)"},{"key":"X-Amz-Cf-Pop","value":"MEL51-P1"},{"key":"X-Amz-Cf-Id","value":"bsyYv5tgEUtHLnZUWoHK8tR39ixYf9-T1QqBru3SmDqb0xhSZri3Mw=="}],"cookie":[],"responseTime":null,"body":"JAPER@api.japer.io@ap-southeast-2::NEXUS healthy"}],"_postman_id":"03578f15-f9b7-4ed5-b5b9-8593468475ae"},{"name":"x","event":[{"listen":"test","script":{"id":"2175164b-1940-4b1f-99df-56a7aae5d369","exec":["pm.test(\"Status code is 200\", function () {"," pm.response.to.have.status(200);","});","","pm.test(\"Body is correct\", function () {"," pm.expect(pm.response.text()).to.include(\"/healthy.\");","});","","pm.test(\"Response time is less than 2 seconds\", function () {"," pm.expect(pm.response.responseTime).to.be.below(2000);","});"],"type":"text/javascript","packages":{}}}],"id":"2e252219-309a-4660-a83c-48513d7f91ee","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"auth":{"type":"apikey","apikey":{"basicConfig":[{"key":"key","value":"x-api-key"},{"key":"value","value":"{{JAPER API Key}}"}]},"isInherited":false},"method":"PATCH","header":[],"body":{"mode":"raw","raw":""},"url":"https://api.japer.io/v1/x/nexus/status","description":"PATCH
\n","urlObject":{"path":["nexus","status"],"host":["https://api.japer.io/v1/x"],"query":[],"variable":[]}},"response":[{"id":"997f0003-09d2-4fe6-a0da-29db92be1bfa","name":"x","originalRequest":{"method":"PATCH","header":[],"body":{"mode":"raw","raw":""},"url":"https://api.japer.io/v1/x/nexus/status"},"status":"OK","code":200,"_postman_previewlanguage":"text","header":[{"key":"Content-Type","value":"text/html"},{"key":"Content-Length","value":"48"},{"key":"Connection","value":"keep-alive"},{"key":"Date","value":"Tue, 26 Nov 2024 07:12:47 GMT"},{"key":"X-Amzn-Trace-Id","value":"Root=1-674574ee-6e97e3162f5739e8042cf4c4;Parent=0f091862fbbab7dc;Sampled=0;Lineage=1:01f7463b:0"},{"key":"x-amzn-RequestId","value":"f9572e44-361f-4f2f-92a4-b3f78c5de1a8"},{"key":"x-amz-apigw-id","value":"B181VF0yywMEmaw="},{"key":"X-Cache","value":"Miss from cloudfront"},{"key":"Via","value":"1.1 0cac85989fc39dec91b3deb3364e4378.cloudfront.net (CloudFront)"},{"key":"X-Amz-Cf-Pop","value":"MEL51-P1"},{"key":"X-Amz-Cf-Id","value":"w7YtsfgPAxN5QuYH4GdUrYzOLv05GqYcogOUvHCGuHLuoLiZh2IFaw=="}],"cookie":[],"responseTime":null,"body":"JAPER@api.japer.io@ap-southeast-2::NEXUS healthy"}],"_postman_id":"2e252219-309a-4660-a83c-48513d7f91ee"},{"name":"x","event":[{"listen":"test","script":{"id":"2175164b-1940-4b1f-99df-56a7aae5d369","exec":["pm.test(\"Status code is 200\", function () {"," pm.response.to.have.status(200);","});","","pm.test(\"Body is correct\", function () {"," pm.expect(pm.response.text()).to.include(\"/healthy.\");","});","","pm.test(\"Response time is less than 2 seconds\", function () {"," pm.expect(pm.response.responseTime).to.be.below(2000);","});"],"type":"text/javascript","packages":{}}}],"id":"5cd03da7-f3f9-43cd-9052-212866cb033f","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"auth":{"type":"apikey","apikey":{"basicConfig":[{"key":"key","value":"x-api-key"},{"key":"value","value":"{{JAPER API Key}}"}]},"isInherited":false},"method":"DELETE","header":[],"body":{"mode":"raw","raw":""},"url":"https://api.japer.io/v1/x/nexus/status","description":"DEL
\n","urlObject":{"path":["nexus","status"],"host":["https://api.japer.io/v1/x"],"query":[],"variable":[]}},"response":[{"id":"c2be1aa7-33e2-40c9-931b-f199fa69182c","name":"x","originalRequest":{"method":"DELETE","header":[],"body":{"mode":"raw","raw":""},"url":"https://api.japer.io/v1/x/nexus/status"},"status":"OK","code":200,"_postman_previewlanguage":"text","header":[{"key":"Content-Type","value":"text/html"},{"key":"Content-Length","value":"48"},{"key":"Connection","value":"keep-alive"},{"key":"Date","value":"Tue, 26 Nov 2024 07:13:11 GMT"},{"key":"X-Amzn-Trace-Id","value":"Root=1-67457507-706d30a8239d8d861e44174d;Parent=41a85056fbe35b98;Sampled=0;Lineage=1:01f7463b:0"},{"key":"x-amzn-RequestId","value":"634db8e5-1144-4c64-a059-83fea85f61d2"},{"key":"x-amz-apigw-id","value":"B185KHR8SwMEShQ="},{"key":"X-Cache","value":"Miss from cloudfront"},{"key":"Via","value":"1.1 0cac85989fc39dec91b3deb3364e4378.cloudfront.net (CloudFront)"},{"key":"X-Amz-Cf-Pop","value":"MEL51-P1"},{"key":"X-Amz-Cf-Id","value":"AF-bG66NCVMwgLjc7FVOFyKwfvUHQpgg1YWMDjcx0TYggr7HSIfueQ=="}],"cookie":[],"responseTime":null,"body":"JAPER@api.japer.io@ap-southeast-2::NEXUS healthy"}],"_postman_id":"5cd03da7-f3f9-43cd-9052-212866cb033f"}],"id":"ef098315-df6e-4879-95fa-79edbefcaaec","description":"The AWS ANY method offers a xenodochial solution for managing all HTTP methods in a single configuration, x. It dynamically routes requests based on the method used, simplifying API Gateway REST setup and supporting diverse backend integrations. This versatility makes it an efficient choice for streamlining API management
\nx\n\nxenodochial
\n
ˌzen-ə-ˈdä-kē-əl
adjective
Friendly to strangers or foreigners; hospitable.
Hospitable to guests; inclined to accommodate others.
Etymology: From Greek xenos (foreign, stranger) + -dochial (related to hosting).
Synonyms: Hospitable, friendly, welcoming, amicable.
The AWS ANY method is xenodochial because it hospitably accommodates all HTTP methods efficiently.
\nThis versatility makes it a powerful tool for managing APIs efficiently. However, with such flexibility, there are security implications to consider, particularly in parameter handling:
\nQuery Strings: commonly used in REST APIs for passing non-sensitive parameters like filters, limits, or sorting options.
\nEven with HTTPS encrypting data in transit, query strings can still appear in server logs, browser histories, and referer headers, which may expose sensitive data if not handled carefully.
\nAvoid including sensitive information in query strings. Use this method primarily for non-sensitive, publicly shareable parameters.
\nHeaders: the preferred method for sending sensitive data such as API keys, authentication tokens, or metadata. They ensure separation of critical data from the resource path and payload.
\nBody Payloads: JSON is ideal for sending large or complex data structures in POST, PUT, or PATCH requests. This is a common method for passing sensitive data like user details or encrypted keys.
\nHTTPS encrypts payloads in transit, ensuring confidentiality. However, improper validation can lead to injection vulnerabilities (e.g., SQL injection, code injection) or schema violations.
\nUse JSON schema validation and sanitize inputs to prevent malicious payloads.
\nPath Parameters: often used to uniquely identify resources in an API (e.g., /id/{id}). They improve readability and route-specific actions efficiently.
Although HTTPS encrypts path parameters in transit, they can still appear in server logs or error traces. Sensitive data in path parameters should be avoided or encrypted.
\nUse path parameters only for identifiers or non-sensitive data. For sensitive data, consider embedding it securely in the request body or headers.
\nBy understanding and applying these considerations, secure and efficient communication with JAPER's AWS servers can be maintained while minimizing risks of data exposure or misuse.
\n","auth":{"type":"noauth","isInherited":false},"event":[{"listen":"prerequest","script":{"id":"f74059b6-5366-4e25-8f4d-f36bb77f3116","type":"text/javascript","exec":[""]}},{"listen":"test","script":{"id":"309dd196-aff1-451a-a634-8282e4684929","type":"text/javascript","exec":[""]}}],"_postman_id":"ef098315-df6e-4879-95fa-79edbefcaaec"}],"id":"7e9490e8-ad52-4ac2-ae10-160832268574","description":"This JAPER API definition is consistent across all JAPER@AWS infrastructure entry points globally. Click the links to Ping the JAPER API Entry Point.
\nAustralia
api.japer[.io|.services|.systems|-ap-southeast-2.net]
Germany
api.japer-eu-central-1.net
Japan
api.japer-ap-northeast-1.net
Singapore
api.japer-ap-southeast-1.net
UK
api.japer-eu-west-2.net
These countries form to make the JAPER-API-GLOBAL-ENTRYPOINTS.
\nAll issued JAPER API Key are bound to a single entry point and accessible exclusively through the SSL-enabled HTTPS protocol on port 443.
\n","_postman_id":"7e9490e8-ad52-4ac2-ae10-160832268574","auth":{"type":"noauth","isInherited":true,"source":{"_postman_id":"f8ad5e90-03e1-47bb-800d-d96bef4744a9","id":"f8ad5e90-03e1-47bb-800d-d96bef4744a9","name":"Developer Support","type":"folder"}}},{"name":"3. Parameters","item":[],"id":"cf61d3ca-401e-4572-916a-9fea7c40ab81","description":"Parameters must follow strict formats and most can be sent URL encoding, JSON bodies, headers, or path parameters.
\n{{Domain}} RFC 1035, Section 2.3.1 defines domain names as alphanumeric labels, 63 characters max, separated by dots, case-insensitive: [name].[top-level-domain]
{{Email Address}} RFC 5322, Section 3.4.1 defines email address syntax as [local-part]@[domain], with strict rules for valid characters and structure: [name]@[domain].[top-level-domain]
{{Telephone Number}} E.164 format: +[Country Code][Subscriber Number], max 15 digits.
{{JAPER API Key}} A secret 40 character string of uppercase letters (A-Z), lowercase letters (a-z), and digits (0-9).
{{JAPER Application ID}} {{JAPER Device ID}} A secret 44 character string of uppercase letters (A-Z), lowercase letters (a-z), digits (0-9) and fullstop and exclamation point (.!), a variant of BASE64.
{{JAPER Command}} Any URL-encoded string.
{{JAPER Customer}} A customer is an Telephone Number, Email Address or Domain.
{{JAPER Customers}} A number of JAPER Customer separated by semi-colon or bar.
\n\nParameters for the JAPER API can be transmitted using various methods, each suited to different use cases and ensuring flexibility in how data is sent and received. The primary methods include URL-encoded variables, JSON bodies, header variables, and path parameters.
\n
When sending more complex or sensitive data, the JSON Body method is preferred. Parameters are structured as key-value pairs within a JSON object, allowing organized and flexible data submission.
\nExample:
\n{\n \"japer\": {\n \"data\": \"JAPER\"\n }\n}\n\nUsage Notes:
\nSet the Content-Type header to application/json to indicate the payload format.
Conform to the JAPER Outcome JSON schema to ensure compatibility.
\nPrimarily used in POST, PUT, PATCH, and DELETE requests where a request body is allowed.
\nHeader Variables are tokens included in the HTTP headers of the request. This method is ideal for transmitting authentication credentials and other metadata required for processing the request.
\nExample:
\nx-api-key: {{JAPER API Key}}\njaper-aid: {{JAPER Application ID}}\njaper-did: {{JAPER Device ID}}\njaper-data: JAPER\n\nUsage Notes:
\nHeaders should be included in the HTTP request header section.
\nIdeal for sensitive information as headers are not visible in URLs.
\nEnsure that all required headers are included to authenticate and authorize the request properly.
\nURL-Encoded Variables are key-value pairs included in the URL query string. This method is suitable for simple data transmission and can be easily used in GET requests.
\nExample:
\nhttps://api.japer.io/v1/x/lookup?data=JAPER\n\nUsage Notes:
\nEnsure that all special characters are properly URL-encoded to prevent errors.
\nSuitable for non-sensitive data due to visibility in the URL.
\nPath Parameters are resource identifiers embedded directly within the URL path. This method is used to specify the exact resource being accessed or manipulated.
\nExample:
\nhttps://api.japer.io/v1/x/lookup/data/JAPER\n\nUsage Notes:
\nPath parameters should be clearly defined in the API endpoint structure.
\nUseful for specifying resources in a RESTful manner.
\nEnsure that path parameters conform to the expected format and encoding standards.
\nThese parameter transmission methods provide the JAPER API with flexibility and security, allowing developers to choose the most appropriate method based on the nature of the data and the requirements of their application. Proper implementation ensures efficient communication with the API and maintains the integrity and security of the information exchanged.
\n","_postman_id":"cf61d3ca-401e-4572-916a-9fea7c40ab81","auth":{"type":"noauth","isInherited":true,"source":{"_postman_id":"f8ad5e90-03e1-47bb-800d-d96bef4744a9","id":"f8ad5e90-03e1-47bb-800d-d96bef4744a9","name":"Developer Support","type":"folder"}}},{"name":"4. Data Models and Schemas","item":[{"name":"JAPER Outcome JSON","item":[{"name":"outcome","item":[{"name":"outcome.data[]","item":[],"id":"d6375934-134b-473b-8971-046511f01218","description":"Type: Array of Objects
Description: Defines the outcome data with various configurable properties.
Required Properties:
\ntype
draw
order
Properties: Each item within the data array is an object with the following properties
type
\nType: String
\nAllowed Values: barcode, barcodebutton, html, image, json, markup, text, url, input-text
Description: Type of data in the value.
\nType: String
\nAllowed Values: all, ar, full, none
Description: Specifies where the data is displayed.
\norder
\nType: Integer
\nRange: -65,536 to 65,536
\nDescription: Determines the draw order of the data.
\naudience
\nType: String
\nDescription: Semi-colon delimited list of JAPER Customers. The device must have the required validations to view the data.
\nid
\nType: String
\nMax Length: 32 characters
\nDescription: Identifier passed as a parameter when a barcodebutton is pressed.
title
\nType: String
\nMax Length: 409 characters
\nDescription: Title of the data element.
\nsize_title
\nType: Integer
\nRange: -32 to 256
\nDefault: 0
\nDescription: Font size of the title.
\nforeground_title
\nType: String
\nPattern: ^#[0-9A-F]{6}$
Description: Title foreground color.
\nbackground_title
\nType: String
\nPattern: ^#[0-9A-F]{6}$
Description: Title background color.
\njustify_title
\nType: String
\nAllowed Values: left, middle, right
Description: Alignment of the title.
\nwidth_title_percent
\nType: String
\nDescription: Width percentage of the title.
\npadding_title
\nType: Integer
\nRange: -32 to 256
\nDefault: 0
\nDescription: Padding around the title.
\npad_top_title
\nType: Integer
\nRange: 0 to 65,536
\nDefault: 0
\nDescription: Top padding of the title.
\npad_left_title
\nType: Integer
\nRange: 0 to 65,536
\nDefault: 0
\nDescription: Left padding of the title.
\npad_right_title
\nType: Integer
\nRange: 0 to 65,536
\nDefault: 0
\nDescription: Right padding of the title.
\npad_bottom_title
\nType: Integer
\nRange: 0 to 65,536
\nDefault: 0
\nDescription: Bottom padding of the title.
\nvalue
\nType: String
\nMax Length: 4,294,967,296 characters
\nDescription: The content value of the data element.
\nallow_copy
\nType: String
\nAllowed Values: no, yes
Default: no
Description: Allows the data to be copied.
\nallow_shot
\nType: String
\nAllowed Values: no, yes
Default: no
Description: Includes the data in screenshots.
\nsize
\nType: Integer
\nRange: -32 to 256
\nDefault: 0
\nDescription: Font size of the value.
\nforeground
\nType: String
\nPattern: ^#[0-9A-F]{6}$
Description: Foreground color of the value.
\nbackground
\nType: String
\nPattern: ^#[0-9A-F]{6}$
Description: Background color of the value.
\njustify
\nType: String
\nAllowed Values: left, middle, right
Description: Alignment of the value.
\nwidth_percent
\nType: String
\nDescription: Width percentage of the value.
\npadding
\nType: Integer
\nRange: 0 to 65,536
\nDefault: 0
\nDescription: Padding around the value.
\npad_top
\nType: Integer
\nRange: 0 to 65,536
\nDefault: 0
\nDescription: Top padding of the value.
\npad_left
\nType: Integer
\nRange: 0 to 65,536
\nDefault: 0
\nDescription: Left padding of the value.
\npad_right
\nType: Integer
\nRange: 0 to 65,536
\nDefault: 0
\nDescription: Right padding of the value.
\npad_bottom
\nType: Integer
\nRange: 0 to 65,536
\nDefault: 0
\nDescription: Bottom padding of the value.
\nbarcodetype
\nType: String
\nAllowed Values: qr, code128
Description: Type of barcode.
\nbarcode_foreground
\nType: String
\nPattern: ^#[0-9A-F]{6}$
Description: Foreground color of the barcode.
\nbarcode_background
\nType: String
\nPattern: ^#[0-9A-F]{6}$
Description: Background color of the barcode.
\nbarcode_link
\nType: String
\nDescription: JAPER Command executed when the barcode is pressed.
\nbarcode_url
\nType: String
\nFormat: URI
\nMax Length: 8192 characters
\nDescription: URL executed when the barcode is pressed.
\nbarcodebutton_foreground
\nType: String
\nPattern: ^#[0-9A-F]{6}$
Description: Foreground color of the barcode button.
\nbarcodebutton_background
\nType: String
\nPattern: ^#[0-9A-F]{6}$
Description: Background color of the barcode button.
\nbarcodebutton_foreground_selected
\nType: String
\nPattern: ^#[0-9A-F]{6}$
Description: Foreground color of the barcode button when selected.
\nbarcodebutton_background_selected
\nType: String
\nPattern: ^#[0-9A-F]{6}$
Description: Background color of the barcode button when selected.
\nbarcodebuttontitle
\nType: String
\nMax Length: 2048 characters
\nDescription: Title of the barcode button.
\ninput_style
\nType: String
\nAllowed Values: inline
Description: Inline text entry field style.
\nqr_error_correction
\nType: String
\nAllowed Values: L, M, H, Q
Description: QR Code error correction level.
\nqr_logo
\nType: String
\nMax Length: 4096 characters
\nDescription: QR Logo in BASE64 format.
\nqr_logo_size
\nType: Integer
\nRange: 1 to 512
\nDescription: Size of the QR logo.
\nqr_logo_background
\nType: String
\nPattern: ^#[0-9A-F]{6}$
Description: Background color of the QR code.
\nqr_logo_margin
\nType: Integer
\nRange: 0 to 64
\nDescription: Space around the logo in the center of the QR code.
\nfiletype
\nType: String
\nAllowed Values: gif, png, jpg, jpeg
Description: File type that the BASE64 value represents.
\nimagewidth
\nType: Integer
\nRange: 0 to 65,536
\nDescription: Width of the image.
\nimageheight
\nType: Integer
\nRange: 0 to 65,536
\nDescription: Height of the image.
\nimage_barcode
\nType: String
\nMax Length: 8192 characters
\nDescription: JAPER Command executed when the image is pressed.
\nimage_url
\nType: String
\nFormat: URI
\nMax Length: 8192 characters
\nDescription: URL executed when the image is pressed.
\nurl_title
\nType: String
\nMax Length: 2048 characters
\nDescription: Title replacing the URL.
\ndatahorizontal
\nType: String
\nAllowed Values: no, yes
Default: no
Description: Determines if nested data arrays draw to the right (yes) instead of down (no).
data
\nType: Array of Objects
\nDescription: Recursive array of data items.
\nType: Object
Description: Defines the outcome with various configurable properties.
Required Properties:
\ntype
lookup
cache or cache_ar and cache_full
Properties:
\nType: String
\nMax Length: 2048 characters
\nDescription: Outcome lookup value.
\nType: String
\nAllowed Values: JAPER, notJAPER
Description:
\nJAPER: Base purple #AC43D9
notJAPER: Base blue #0000FF
Type: Integer
\nRange: 1 to 3,122,064,000
\nDescription: Number of seconds before the JAPER Outcome is purged from memory.
\nType: Integer
\nRange: 1 to 3,122,064,000
\nDescription: Seconds before the Outcome is purged from memory when viewed in AR.
\nType: Integer
\nRange: 1 to 3,122,064,000
\nDescription: Seconds before the Outcome is purged from memory when viewed in Full.
\nType: String
\nAllowed Values: back-camera | front-camera | light-on | light-off | light-toggle | main-menu | purge-validations | disable-app | manage-validations | validate-email | validate-sms | enter-validation-code | user-settings | set-app-start-pin | remove-app-start-pin | app-start-pin-failure-action | select-font | clear-memory-cache | reload-device-status
\nDescription: Invokes various parts of the app.
\nType: String
\nAllowed Values: no, yes
Default: no
Description: Forces the Outcome to display in full screen.
\nauto_full_on_cache
\nType: String
\nAllowed Values: no, yes
Default: no
Description: Forces full screen display only the first time the Outcome is loaded and cached.
\nauto_ar_url
\nType: String
\nFormat: URI
\nMax Length: 8192 characters
\nDescription: Automatically opens a URL when the Outcome is displayed in AR.
\nauto_full_url
\nType: String
\nFormat: URI
\nMax Length: 8192 characters
\nDescription: Automatically opens a URL when the Outcome is displayed in Full.
\nvibrate
\nType: Integer
\nRange: 1 to 60,000
\nDescription: Duration in milliseconds to vibrate when the Outcome is displayed in Full.
\nar_background
\nType: String
\nPattern: ^#[0-9A-F]{6}$
Description: AR background color.
\nar_border_north_west
\nType: String
\nPattern: ^#[0-9A-F]{6}$
Description: North-west AR border corner color.
\nar_border_north_east
\nType: String
\nPattern: ^#[0-9A-F]{6}$
Description: North-east AR border corner color.
\nar_border_south_west
\nType: String
\nPattern: ^#[0-9A-F]{6}$
Description: South-west AR border corner color.
\nar_border_south_east
\nType: String
\nPattern: ^#[0-9A-F]{6}$
Description: South-east AR border corner color.
\nar_cache_off
\nType: String
\nAllowed Values: no, yes
Default: no
Description: Prevents the AR South-east border from indicating default white if the information is cached.
\noverride_japer
\nType: String
\nPattern: ^#[0-9A-F]{6}$
Description: Overrides the default JAPER Purple color.
\nar_override_japer
\nType: String
\nPattern: ^#[0-9A-F]{6}$
Description: Overrides the JAPER Purple color for AR display.
\nfull_override_japer
\nType: String
\nPattern: ^#[0-9A-F]{6}$
Description: Overrides the JAPER Purple color for Full display.
\nwidth_full
\nType: Number
\nRange: 0.01 to 8192
\nDescription: Percentage width of the Full Outcome.
\nfull_cache_expired
\nType: String
\nDescription: JAPER Command executed upon cache expiry.
\nfull_control
\nType: String
\nAllowed Values: no, yes
Default: no
Description: Hides the JAPER Logo and Back Arrow, limiting exits to those provided by the Outcome creators.
\nfull_click
\nType: String
\nPattern: ^#[0-9A-F]{6}$
Description: Color of the \"Click to See\" button.
\nfull_click_title
\nType: String
\nMax Length: 2048 characters
\nDescription: Title of the \"Click to See\" button.
\nfull_click_title_foreground
\nType: String
\nPattern: ^#[0-9A-F]{6}$
Description: Color of the \"Click to See\" button title.
\nfull_exit_barcode
\nType: String
\nMax Length: 8192 characters
\nDescription: JAPER Command executed when exiting the Outcome via the JAPER Logo or Exit Button.
\nfull_exit_url
\nType: String
\nFormat: URI
\nMax Length: 8192 characters
\nDescription: URL executed when exiting the Outcome via the JAPER Logo or Exit Button.
\nfull_allow_landscape
\nType: String
\nAllowed Values: yes, no
Default: yes
Description: Allows the Full Outcome to display in landscape orientation.
\nfull_title_0
\nType: String
\nMax Length: 64 characters
\nDescription: Changes the Back Arrow to a title.
\nfull_title_1
\nType: String
\nMax Length: 64 characters
\nDescription: Changes the first title line.
\nfull_title_2
\nType: String
\nMax Length: 64 characters
\nDescription: Changes the second title line.
\nfull_hide_all
\nType: String
\nAllowed Values: no, yes
Default: no
Description: Hides all elements.
\nfull_hide_titles
\nType: String
\nAllowed Values: no, yes
Default: no
Description: Hides the titles.
\nfull_hide_japer_logo
\nType: String
\nAllowed Values: no, yes
Default: no
Description: Hides the JAPER Logo.
\nfull_hide_all_buttons
\nType: String
\nAllowed Values: no, yes
Default: no
Description: Hides all buttons to provide more space for content.
\nfull_hide_help_button
\nType: String
\nAllowed Values: no, yes
Default: no
Description: Hides the Help Button.
\nfull_hide_copy_button
\nType: String
\nAllowed Values: no, yes
Default: no
Description: Hides the Copy Button.
\nfull_hide_shot_button
\nType: String
\nAllowed Values: no, yes
Default: no
Description: Hides the Screen Shot Button.
\nfull_hide_exit_button
\nType: String
\nAllowed Values: no, yes
Default: no
Description: Hides the Exit Button.
\nfull_help_barcode
\nType: String
\nMax Length: 8192 characters
\nDescription: JAPER Command executed when the Help Button is pressed.
\nfull_help_url
\nType: String
\nFormat: URI
\nMax Length: 8192 characters
\nDescription: URL opened when the Help Button is pressed.
\ndatahorizontal
\nType: String
\nAllowed Values: no, yes
Default: no
Description: Determines if the data array draws to the right (yes) instead of down (no).
data
\nType: Array of Objects
\nDescription: An array of recursive data items defining various elements within the Outcome.
\nAn OpenAPI v3.1 JSON definition specifies REST API structure, endpoints, and data models for documentation and integration.
\nUnder Construction
The JAPER Outcome JSON Schema defines the structure and behavior of JAPER Outcomes created and processed. The execution and visibility depending on the JAPER Device Customer Validations. This ensures only validated JAPER Customers can access or interpret JAPER Outcomes, enforcing a permissions-driven model.
\nwww.japer.cloud/decrypt
Allows JAPER Outcome to be searched.
www.japer.cloud/reflector
Allows JAPER Outcome to be created and used in a sandpit.
ID: http://www.japer.cloud/json/outcome.json
Schema Version: http://json-schema.org/version-2023-09-22/schema#
Type: Object
Required Properties:
\noutcome{\n \"outcome\": {}\n}\n\nThe JAPER Outcome JSON Schema is the ...
\n","_postman_id":"352d69f4-043d-4e4d-8083-124a06c1602b","auth":{"type":"noauth","isInherited":true,"source":{"_postman_id":"f8ad5e90-03e1-47bb-800d-d96bef4744a9","id":"f8ad5e90-03e1-47bb-800d-d96bef4744a9","name":"Developer Support","type":"folder"}}},{"name":"5. Request Format","item":[{"name":"Idempotent Requests","item":[],"id":"07f48b97-78c3-4fe1-be6a-90bf370a08dd","description":"The japer-idempotency variable ensures that repeated requests to the JAPER API do not trigger duplicate operations. Immutable by design, it allows the JAPER Nexus to identify prior executions: if a request with the same variable exists, the cached result is returned; otherwise, the request is processed, and the outcome is stored. This guarantees reliable, consistent operations, preventing unintended duplication while enhancing system integrity and efficiency.
The recommended minimum japer-idempotency size is 128 bits, typically represented as a UUIDv4 (Universally Unique Identifier) string. This provides sufficient entropy to avoid collisions while ensuring compatibility with standard systems and APIs. A 36-character string format (e.g., 550e8400-e29b-41d4-a716-446655440000) balances uniqueness, readability, and efficiency.
The best way to generate a UUIDv4 or better is to use a cryptographically secure random number generator to ensure uniqueness and prevent predictable values.
\n","_postman_id":"07f48b97-78c3-4fe1-be6a-90bf370a08dd","auth":{"type":"noauth","isInherited":true,"source":{"_postman_id":"f8ad5e90-03e1-47bb-800d-d96bef4744a9","id":"f8ad5e90-03e1-47bb-800d-d96bef4744a9","name":"Developer Support","type":"folder"}}},{"name":"Pagination, Filtering and Sorting","item":[],"id":"bfb073c1-dcf0-4d14-a6e7-9035e284e0f8","description":"Not required.
\n","_postman_id":"bfb073c1-dcf0-4d14-a6e7-9035e284e0f8","auth":{"type":"noauth","isInherited":true,"source":{"_postman_id":"f8ad5e90-03e1-47bb-800d-d96bef4744a9","id":"f8ad5e90-03e1-47bb-800d-d96bef4744a9","name":"Developer Support","type":"folder"}}}],"id":"e839eaf0-5d04-4527-9516-85c293c6b159","description":"In most cases, a request to the JAPER API primarily returns status codes, with encryption and decryption being the main exceptions where JSON objects can be both sent and received.
\nThe JSON Body parameters are structured as key-value pairs under the japer object, allowing organised and flexible data submission for API commands and responses:
{\n \"japer\" : {\n \"data\": \"JAPER\"\n }\n}\n\nWhen you choose to send JSON payloads, please make sure to use Content-Type: application/json in your headers and conform to the JAPER Outcome JSON schema. The maximum payload size for the AWS API Gateway is 10 MB.
Our REST API supports the JSON data format. Every parameter / payload you pass (with very few exceptions, e.g., when you upload files) can be formatted in JSON and our API can be instructed to return results in JSON.
When you choose to send JSON payloads, please make sure to use Content-Type: application/json in your headers.
The JAPER API generally returns response codes for informational purposes. However, for decrypt, lookup and execute, the JSON response includes the \"outcome\" field as per the JAPER Outcome JSON Schema and may also include the \"japer\" field.
\n{\n \"japer\" : {},\n \"outcome\": { \"$ref\": \"https://www.japer.tools/json-schema/outcome.json\" }\n}\n\n2xx\n\nIf you receive a HTTP status code that starts with 2 then all is well.
\n
/ping: Completed successfully.
/decrypt: Outcome is JAPER.
/device/purge: Completed successfully.
/device/kill: Completed successfully.
/device/status: Status is known.
/validation/attempt: PIN failed validation.
/validation/status: Customer is known.
/device/create: Completed successfully.
/validation/attempt: PIN was validated.
/validate/email: Email PIN was sent.
/validate/sms: SMS PIN was sent.
/validate/domain: Domain was validated.
/validation/status: Customer has opted In.
/validate/sms: Not Sent.
/validation/status: Customer is Opted Out.
/decrypt: Outcome is NotJAPER.
/device/status: Status is Unknown.
/validation/status: Customer is Unknown.
The JAPER-API-GATEWAY sees each JAPER-API-KEY as a JAPER-CUSTOMER within a global pool, where both global and individual customer allowances dictate request limits. The gateway closely monitors 429 errors to evaluate whether an API Key adheres to its assigned pool limits. Frequent 429 errors indicate overuse or inadequate handling, which may lead to reassignment to a shallower pool with stricter restrictions. Conversely, consistent compliance with rate limits and proper error handling can qualify a key for reassignment to a deeper pool, such as E or F, providing higher request allowances.
\nEach API Key operates within a structured hierarchy of global and customer-specific allowances, ensuring fair access while maintaining system stability.
\nGlobal Pool Allowance (Shared Across All Customers)
\nCustomer Pool Allowance (Per API Key Within the Global Pool)
\nThis structure ensures that each API Key operates within a fair and scalable system, balancing customer access with overall system performance.
\n","_postman_id":"2d612111-a093-4419-9f29-e55ed1372a6b","auth":{"type":"noauth","isInherited":true,"source":{"_postman_id":"f8ad5e90-03e1-47bb-800d-d96bef4744a9","id":"f8ad5e90-03e1-47bb-800d-d96bef4744a9","name":"Developer Support","type":"folder"}}}],"id":"de20c7d4-1403-4ef1-887c-aa0c4a28f406","description":"4xx\n\nIf you receive a HTTP status code that starts with 4 there's something wrong on your side, your request is wrong in some way.
\n
Requests have exceeded the rate limits or quotas for your JAPER API Key.
\nCheck the Retry-After in the header: this is the suggested number of seconds you should wait before retrying, if present you should respect the recommended delay.
Understand your JAPER API Key limits and quotas.
\nRetry using exponential backoff with jitter.
\nIf encrypting consider encryption batching.
\n5xxIf you receive a HTTP status code that starts with 5 there's something wrong on our side, terribly terribly wrong. Alarms will have been triggered so you can be assured of our attention to these errors.
\n","_postman_id":"afc1c010-a0cc-4b7f-aaf5-3ae53170a014","auth":{"type":"noauth","isInherited":true,"source":{"_postman_id":"f8ad5e90-03e1-47bb-800d-d96bef4744a9","id":"f8ad5e90-03e1-47bb-800d-d96bef4744a9","name":"Developer Support","type":"folder"}}}],"id":"79652056-69b1-465c-843b-33829e9654c6","description":"See: AWS API Gateway Response Types
\n","_postman_id":"79652056-69b1-465c-843b-33829e9654c6","auth":{"type":"noauth","isInherited":true,"source":{"_postman_id":"f8ad5e90-03e1-47bb-800d-d96bef4744a9","id":"f8ad5e90-03e1-47bb-800d-d96bef4744a9","name":"Developer Support","type":"folder"}}},{"name":"8. Cookbook","item":[],"id":"2915467f-01f8-4d93-a2e1-9ba33953e208","description":"1. Review the Documentation
Start by thoroughly reading this API documentation. Identify key features, authentication methods, response structures, and rate limits. Highlight sections relevant to your project and note any potential edge cases or constraints that may affect implementation.
2. Set Up a Sandbox Environment
Create a sandbox or use the provided test console to experiment safely. This isolated environment allows you to:
Validate API endpoints
\nConfirm data formats
\nTroubleshoot errors without impacting live systems
\n3. Experiment and Test
Begin making sample requests to different endpoints. Monitor responses to ensure they match expectations. Utilize version control to track changes and maintain a history of your experiments. Regularly check logs to identify and resolve issues promptly.
4. Develop Structured Code
When you’re comfortable with the API’s functionality, start integrating it into your project. Write well-structured code with clear abstractions to simplify future maintenance. Implement robust error handling to gracefully manage any API failures or unexpected responses.
5. Implement Security Measures
Secure your integration by managing tokens effectively and setting up appropriate access controls. Ensure that sensitive data is handled securely and that your application complies with any relevant security standards or best practices.
6. Test Thoroughly in Staging
Before going live, deploy your integration to a staging or beta environment. Conduct comprehensive testing to verify that the API functions correctly within your project. Use a detailed checklist to ensure all aspects of the integration are stable and reliable.
7. Move to Production
Once testing is complete and you’re confident in the integration’s performance, push the API into your production environment. Continuously monitor its performance and maintain documentation to support ongoing maintenance and future updates.
By following these best practices, you can effectively introduce and integrate a new API into your project, ensuring a smooth and reliable implementation.
\n","_postman_id":"2915467f-01f8-4d93-a2e1-9ba33953e208","auth":{"type":"noauth","isInherited":true,"source":{"_postman_id":"f8ad5e90-03e1-47bb-800d-d96bef4744a9","id":"f8ad5e90-03e1-47bb-800d-d96bef4744a9","name":"Developer Support","type":"folder"}}},{"name":"9. Examples and Use Cases","item":[],"id":"be80b0f5-36c2-49bf-ae93-7d5688344806","description":"Explore examples to understand how JAPER API can be leveraged in various contexts.
\n","_postman_id":"be80b0f5-36c2-49bf-ae93-7d5688344806","auth":{"type":"noauth","isInherited":true,"source":{"_postman_id":"f8ad5e90-03e1-47bb-800d-d96bef4744a9","id":"f8ad5e90-03e1-47bb-800d-d96bef4744a9","name":"Developer Support","type":"folder"}}},{"name":"10. JAPER Ecosystem","item":[{"name":"JAPER API","item":[],"id":"32ae3e9d-c7e2-4bef-9da3-d6c75d814bc2","description":"\n\nThis document is the starting point of the JAPER Ecosystem, introducing the foundational JAPER API, its capabilities, and seamless Postman integration for efficient endpoint testing and management.
\n","auth":{"type":"noauth","isInherited":false},"event":[{"listen":"prerequest","script":{"id":"63c225d4-6d45-4c41-83f3-6855deaabaa9","type":"text/javascript","exec":[""]}},{"listen":"test","script":{"id":"221eba70-06d1-46f7-9a6b-a9f4ca503201","type":"text/javascript","exec":[""]}}],"_postman_id":"32ae3e9d-c7e2-4bef-9da3-d6c75d814bc2"},{"name":"JAPER Website","item":[{"name":"www.japer.technology","item":[],"id":"5e01f3c5-1848-477b-ace2-f7c912bcccb8","description":"The JAPER Technology website is the central hub for logging in, accessing JAPER services, and managing core functionalities.
\nwww.japer.technology/introduction
\nwww.japer.technology/membership
\n\n\n","_postman_id":"5e01f3c5-1848-477b-ace2-f7c912bcccb8","auth":{"type":"noauth","isInherited":true,"source":{"_postman_id":"7114e528-2111-49ac-8252-28ac8beacdb4","id":"7114e528-2111-49ac-8252-28ac8beacdb4","name":"10. JAPER Ecosystem","type":"folder"}}},{"name":"www.japer.cloud","item":[],"id":"98bfe3d6-7ee7-4c77-b91a-e40d4785a2fc","description":"The JAPER Cloud website act as firewall to the JAPER API, facilitating dynamic content delivery, data-driven interactions, and seamless integration with automation workflows through web interfaces and API connectivity.
\nwww.japer.cloud/decrypt Allows JAPER Outcome to be found and decrypted.
\nwww.japer.cloud/reflector Allows JAPER Outcome to be created and viewed in a sandpit.
\n","_postman_id":"98bfe3d6-7ee7-4c77-b91a-e40d4785a2fc","auth":{"type":"noauth","isInherited":true,"source":{"_postman_id":"7114e528-2111-49ac-8252-28ac8beacdb4","id":"7114e528-2111-49ac-8252-28ac8beacdb4","name":"10. JAPER Ecosystem","type":"folder"}}},{"name":"www.japer.xyz","item":[],"id":"c1a6903b-41d8-4b3c-afe9-3cc657f5b738","description":"The JAPER XYZ website contains documentation, agreements, and resources for understanding and utilising the JAPER Ecosystem.
\nhttps://www.japer.xyz/privacy-policy
\nhttps://www.japer.xyz/billing-policy
\nhttps://www.japer.xyz/terms-and-conditions
\n","_postman_id":"c1a6903b-41d8-4b3c-afe9-3cc657f5b738","auth":{"type":"noauth","isInherited":true,"source":{"_postman_id":"7114e528-2111-49ac-8252-28ac8beacdb4","id":"7114e528-2111-49ac-8252-28ac8beacdb4","name":"10. JAPER Ecosystem","type":"folder"}}}],"id":"2cb48567-59e8-4e73-bcab-df8b3409c4fe","description":"\n\nThe www.japer.technology website serves as the primary platform for user logins and accessing JAPER’s core services. The www.japer.cloud provides a range of utilities and tools, which can also be accessed through the JAPER App for mobile convenience. For comprehensive resources, technical information, and operational guidelines, the www.japer.xyz website houses all relevant documentation. Together, these platforms provide seamless access to JAPER's ecosystem.
\n","_postman_id":"2cb48567-59e8-4e73-bcab-df8b3409c4fe","auth":{"type":"noauth","isInherited":true,"source":{"_postman_id":"7114e528-2111-49ac-8252-28ac8beacdb4","id":"7114e528-2111-49ac-8252-28ac8beacdb4","name":"10. JAPER Ecosystem","type":"folder"}}},{"name":"JAPER App","item":[{"name":"JAPER App Pages","item":[],"id":"fb3ed0b4-99b0-412f-a836-339df4b1e979","description":"When the JAPER App starts the Back Camera Scanner starts...
\nBack Camera Scanner
The default starting page of the JAPER App, displayed after the App Start PIN screen (if enabled). Scans barcodes using the back camera after app launch.
Rest Mode
Automatically displays a barcode in full screen when no barcode is detected for a defined period (rest_after seconds, usually 120).
AR Outcome
Displays JAPER Data in augmented reality style when a barcode is continuously scanned, provided the device owner allows it.
Full Outcome
Displays a scanned barcode’s JAPER Outcome in full screen.
Full Outcome Landscape
Similar to Full Outcome but optimized for landscape view when the device is rotated, if enabled by the Outcome creator.
Main Menu
Access a menu of app options by pressing the JAPER Logo while scanning.
Help
If displayed provides context-sensitive online help.
Back Camera Light (On/Off)
Toggles the back camera light. Light is off by default when the app starts or goes into the background. Only available within the back camera scanner.
Command Button
Access JAPER command options for the device. Commands allow secure interaction with JAPER functionality.
About Us
Provides information about JAPER Technology and the JAPER App.
API Entrypoint
Displays the JAPER API entry point the app is connected to, based on the device’s region.
Manage Validations
\nLists validations on the device and provides management options for each.
\nValidate Email
Sends a 6-digit validation code to the email address.
Validate Domain
Displays DNS entries required for domain validation. Available under Manage Validations for validated email accounts.
Validate SMS
Sends a 6-digit validation code to the registered SMS number.
Enter Validation Code
Allows manual entry of a 6-digit validation code for validation purposes.
User Settings
Access user-specific settings and actions.
Set/Remove App Start PIN
Configures or removes the PIN required to start the app.
Select PIN Failure Action
Determines the app’s behavior after a failed PIN attempt.
Select App Font
Customizes the font used in the app interface.
Clear Memory Cache
Clears the app’s memory cache to reset cached Outcomes.
Switch to Front/Back Camera
\nSwitches between the front and back camera scanners.
\nPurge Validations
Deletes all validations on the device.
Disable App
Disables the app, making it inert until reinstalled. Available only when not already activated.
App Version
Displays the current app version and build number.
\n\nThe JAPER App is a lightweight client application designed to deliver secure, interactive experiences by interpreting data from the JAPER API. By seamlessly integrating advanced security features like encryption, decryption, and validation, the JAPER App empowers developers to provide real-time, user-friendly interfaces that meet modern security demands.
\n![\"JAPER](\"https://i.imgur.com/c2NG1MP.png\")
![\"JAPER](\"https://i.imgur.com/N9cKjJx.png\")
At its core, the JAPER App renders JAPER Outcome, a structured, API-generated responses tailored to specific interactions or commands. These Outcomes, authenticated through API Keys, AIDs (Application Identifiers), and DIDs (Device Identifiers), include dynamic elements such as barcodes, augmented reality (AR) interfaces, and personalized content, ensuring compliance, scalability, and customization.
\nThe JAPER App transforms JSON-based Outcomes into intuitive displays, supporting features like AR overlays, encrypted messaging, and secure validation prompts. It also enforces critical parameters, such as access control, data expiration, and caching rules, ensuring that every user interaction remains secure, consistent, and reliable.
\nBy serving as the user-facing interface of the JAPER Ecosystem, the JAPER App bridges the gap between secure backend processes and real-time user engagement. This integration enables developers to create cutting-edge applications that combine robust security with seamless interactivity.
\nJAPER-APP-FLUSH
\n","_postman_id":"3f634ef0-a2b5-4314-bbfa-83e845ce7b1f","auth":{"type":"noauth","isInherited":true,"source":{"_postman_id":"7114e528-2111-49ac-8252-28ac8beacdb4","id":"7114e528-2111-49ac-8252-28ac8beacdb4","name":"10. JAPER Ecosystem","type":"folder"}}},{"name":"JAPER Data","item":[],"id":"3925210f-890b-433c-a5a0-525b78c8cc94","description":"\n\nJAPER-DATA is encrypted JAPER-OUTCOME at the intersection of:
\nCreator: A validated JAPER Customer, such as an Email, SMS, or Domain DNS
\nOwners: JAPER Customers, such as an Email, SMS, or Domain DNS, that determines access permissions.
\nReference: A unique identifier linking the outcome to a specific dataspace, namespace or keyspace.
\nThis design ensures that JAPER-DATA is accessible at the intersection of these components, enabling secure, permissions-driven encryption and decryption.
\n","auth":{"type":"noauth","isInherited":false},"event":[{"listen":"prerequest","script":{"id":"63c225d4-6d45-4c41-83f3-6855deaabaa9","type":"text/javascript","exec":[""]}},{"listen":"test","script":{"id":"221eba70-06d1-46f7-9a6b-a9f4ca503201","type":"text/javascript","exec":[""]}}],"_postman_id":"3925210f-890b-433c-a5a0-525b78c8cc94"},{"name":"JAPER Email","item":[],"id":"f89ba3c3-2fc3-4a61-a5c3-06358ba735fa","description":"\n\nJAPER Email serves as an intuitive gateway to the JAPER API, facilitating automation via email, data extraction, communication management, and smooth workflow integration through structured commands. It also thoroughly verifies each sender by conducting multiple authentication checks and in-depth security analysis prior to processing:
\nVALIDATED: The email address is confirmed using the JAPER App.
\nSPAM: Unwanted and unsolicited bulk emails are filtered out.
\nVIRUS: Malicious software is detected and blocked.
\nSPF: The sender’s IP address is verified to prevent spoofing.
\nDKIM: A digital signature ensures both the integrity of the email content and the authenticity of the sender.
\nDMARC: This combines SPF and DKIM to enforce strict email authentication policies. These measures ensure that all emails processed by JAPER Email are secure and originate from authenticated users.
\nThis authentication framework ensures that only a verified email address can issue commands to the associated AI agent. This controlled access prevents unauthorized or spoofed messages from affecting the AI agent’s behavior, effectively allowing the verified email address to serve as a secure key for controlling the AI agent’s actions.
\n[ask|question]@japer.services returns JAPER-GPT interaction.
barcode[s]@japer.services returns barcode images.
deeplink@japer.services returns deeplinks as barcode images.
defcon@japer.services returns confirmation of security lockdown.
opt[-][in|out]@japer.services sets and returns JAPER Email Customer status.
ping@japer.services returns proof that the email was processed by JAPER Technology.
status@japer.services returns the JAPER Email Customer and AWS SES security assessment.
validat[e|ion]@japer.services returns JAPER Validation interaction.
[agent|ai|bot|chat|cot|droid|llm|robot]@japer.services returns AI interaction.
[remember|forget]@japer.services returns AI interaction.
dalle@japer.services returns an AI interaction.
d[d]b@japer.services returns confirmation of a JAPER Database interaction.
decrypt[ion]@japer.services returns confirmation of JAPER Data Decryption.
encrypt[ion]@japer.services returns confirmation of JAPER Data Encryption.
pod@japer.services returns confirmation of a JAPER Pod Operation.
caller@japer.services returns a PIN for interaction identity validation.
[gpt|question]@japer.services returns JAPER GPT interaction.
keyspace@japer.services returns JAPER Keyspace interaction.
[message|msg]@japer.services returns confirmation of JAPER Message Sent.
note@japer.services returns confirmation of JAPER Note Sent.
webhook@japer.services returns confirmation of a JAPER Webhook interaction.
hook@japer.services shallow processes a JAPER Webhook.
[cmd|command]@japer.services
[a|an]@japer.services
api@japer.services
email@japer.services
[j|japer]@japer.services
privacy@japer.services
All return confirmation of JAPER Command interaction.
[ctrl|control]@japer.services
[cli|command-line-interface]@japer.services
[esi|email-subject-interface]@japer.services
secure@japer.services
shell@japer.services
All return confirmation of JAPER Command interaction using Email Header information only.
\n\nThe JAPER Keyspace operates within the JAPER Namespace, defining the namespace that governs encrypted data management and access control. The namespace is dynamically tied to JAPER Customer Validation, meaning access and permissions are determined by the customer's validation status, such as Email, SMS, or Domain DNS verification. This ensures that only validated customers can interact with specific keyspaces, enabling secure, permissions-driven encryption, decryption, and resource management. The validation dependency provides a hierarchical access model, where customer validation directly influences the namespace functionality and scope within the JAPER Ecosystem.
\nPDF: JAPER Keyspace Manual
\n","auth":{"type":"noauth","isInherited":false},"event":[{"listen":"prerequest","script":{"id":"d40a684a-b2d9-4d2f-a3ab-2d87e3c892ba","type":"text/javascript","exec":[""]}},{"listen":"test","script":{"id":"88fa5cb5-bb12-4442-8d82-d0fa66b2530a","type":"text/javascript","exec":[""]}}],"_postman_id":"eabbf4cc-c7c5-4096-a388-a11dcdf0325c"},{"name":"JAPER Namespace","item":[{"name":"Index of Namespaces","item":[],"id":"b8c5ff17-d5c1-45e1-b2fb-d90f32b413ab","description":"","_postman_id":"b8c5ff17-d5c1-45e1-b2fb-d90f32b413ab","auth":{"type":"noauth","isInherited":true,"source":{"_postman_id":"bf9f1680-493b-4bbb-9088-f23c7aebc929","id":"bf9f1680-493b-4bbb-9088-f23c7aebc929","name":"JAPER Namespace","type":"folder"}}},{"name":"JAPER-API","item":[{"name":"JAPER-API-VERSION","event":[{"listen":"test","script":{"id":"3cbb5c75-2ad6-485d-a2c9-62a4f0d2fa23","exec":["pm.test(\"Status code is 200\", function () {"," pm.response.to.have.status(200);","});","","pm.test(\"Response time is less than 3 seconds\", function () {"," pm.expect(pm.response.responseTime).to.be.below(3000);","});"],"type":"text/javascript","packages":{}}}],"id":"4b5791ba-82c7-451f-aa00-3e27c5e240ab","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"auth":{"type":"apikey","apikey":{"basicConfig":[{"key":"key","value":"x-api-key"},{"key":"value","value":"{{JAPER API Key}}"}]},"isInherited":false},"method":"GET","header":[{"key":"japer-aid","value":"{{JAPER Application ID}}"},{"key":"japer-did","value":"{{JAPER Device ID}}"},{"key":"japer-data","value":"JAPER-API-VERSION"}],"body":{"mode":"raw","raw":""},"url":"https://api.japer.io/v1/x/execute","description":"\n\nReturns the JAPER API Version as JAPER JSON Outcome.
\n
200 = OK
This is the corresponding JAPER App barcode:
\n![\"JAPER-API-VERSION\"](\"https://i.imgur.com/4eXh1hk.png\")
\n\nReturns the JAPER API Version as JAPER JSON Outcome.
\n
200 = OK
This is the corresponding JAPER App barcode:
\n![\"JAPER-API-ACTIVATE-GLOBAL\"](\"https://i.imgur.com/DkrzjH4.png\")
The JAPER API operates as the JAPER-API namespace, providing a structured framework for executing commands and managing resources. It organizes API functions hierarchically, supporting encryption, validation, and device interactions, ensuring precise and consistent operations within the JAPER Ecosystem.
\nThis is the JAPER-API namespace for JAPER-API-ENDPOINTS:
\n/ping: JAPER-API-PING-LEVEL-1
/v1/ping: JAPER-API-PING-LEVEL-2
/v1/x/nexus/status: JAPER-API-PING-LEVEL-3
/v1/x/device/create: JAPER-API-DEVICE-CREATE
/v1/x/device/status: JAPER-API-DEVICE-STATUS
/v1/x/device/purge: JAPER-API-DEVICE-PURGE
/v1/x/device/kill: JAPER-API-DEVICE-KILL
/v1/x/encrypt: JAPER-API-ENCRYPT
/v1/x/decrypt: JAPER-API-DECRYPT
/v1/x/lookup: JAPER-API-LOOKUP
/v1/x/execute: JAPER-API-EXECUTE
/v1/x/validation/attempt: JAPER-API-VALIDATION-ATTEMPT
/v1/x/validate/domain: JAPER-API-VALIDATE-DOMAIN
/v1/x/validate/email: JAPER-API-VALIDATE-EMAIL
/v1/x/validate/sms: JAPER-API-VALIDATE-SMS
/v1/x/validation/status: JAPER-API-VALIDATION-STATUS
\n\nReturns the near minimum JAPER Outcome definition that in computer programming terms is the JAPER's \"Hello World!\"
\n
200 = OK
\n\nExecutes JAPER-NAMESPACE
\n
200 = OK
https://www.japer.vision/?j=JAPER-NAMESPACE
\nhttps://www.japer.cloud/decrypt?j=JAPER-NAMESPACE
\nhttps://www.japer.cloud/barcode?j=JAPER-NAMESPACE
\n","urlObject":{"host":["https://api.japer.io/v1/x/execute"],"query":[],"variable":[]}},"response":[{"id":"c57aa659-76ff-4a61-aaf0-89348e13a8a7","name":"JAPER-NAMESPACE","originalRequest":{"method":"GET","header":[{"key":"japer-aid","value":"{{JAPER Application ID}}"},{"key":"japer-did","value":"{{JAPER Device ID}}"},{"key":"japer-data","value":"JAPER-NAMESPACE"}],"body":{"mode":"raw","raw":""},"url":"https://api.japer.io/v1/x/execute"},"status":"OK","code":200,"_postman_previewlanguage":"json","header":[{"key":"Content-Type","value":"application/json","description":"","type":"text"}],"cookie":[],"responseTime":null,"body":"{\n \"outcome\": {\n \"full_allow_landscape\": \"no\",\n \"cache\": 60,\n \"cache_ar\": 60,\n \"cache_full\": 31536000,\n \"type\": \"JAPER\",\n \"lookup\": \"JAPER-NAMESPACE\",\n \"auto_full\": \"yes\",\n \"width_full\": 0.98,\n \"full_title_1\": \"Namespace\",\n \"full_title_2\": \" \",\n \"full_hide_all_buttons\": \"yes\",\n \"full_override_japer\": \"#000000\",\n \"ar_border_north_east\": \"#FFFFFF\",\n \"ar_cache_off\": \"yes\",\n \"data\": [\n {\n \"draw\": \"ar\",\n \"order\": 1,\n \"justify\": \"middle\",\n \"type\": \"text\",\n \"size\": -6,\n \"value\": \"JAPER\"\n },\n {\n \"draw\": \"ar\",\n \"order\": 2,\n \"justify\": \"middle\",\n \"type\": \"text\",\n \"size\": -6,\n \"value\": \"Namespace\"\n },\n {\n \"draw\": \"full\",\n \"order\": 3,\n \"justify\": \"middle\",\n \"type\": \"text\",\n \"size\": 2,\n \"value\": \"NAMESPACE provides command protocols with recursion\",\n \"padding\": 4\n },\n {\n \"draw\": \"full\",\n \"order\": 4,\n \"justify\": \"middle\",\n \"type\": \"barcodebutton\",\n \"size\": -4,\n \"barcodebutton_foreground\": \"#FFFFFF\",\n \"barcodebutton_background\": \"#AC43D9\",\n \"barcodebuttontitle\": \"JAPER Command\",\n \"value\": \"JAPER-COMMAND\",\n \"padding\": 4,\n \"background\": \"#000000\",\n \"background_title\": \"#000000\"\n },\n {\n \"draw\": \"full\",\n \"order\": 5,\n \"justify\": \"middle\",\n \"type\": \"image\",\n \"filetype\": \"png\",\n \"width\": \"44\",\n \"height\": \"44\",\n \"pad_top\": 64,\n \"pad_bottom\": 2,\n \"value\": \"iVBORw0KGgoAAAANSUhEUgAAACwAAAAsCAYAAAAehFoBAAAAAXNSR0IArs4c6QAAAARnQU1BAACxjwv8YQUAAAAJcEhZcwAADsQAAA7EAZUrDhsAAATDSURBVFhH7Zf7SxxXFMf3YVyS2lp/0miMbYQu2kV0THRTayKatXmQYFpjxYjYIpjKakxoCSVNIf9ACVRsIb8UYqU/WQLFdhcT1DTBsEK0RFwUtbGBmmrTNlul0d09nXPn3JnZp7vsbEjAz3KYe8+ZOfc79zV3dfCCsSU42WwJTjZbgiMxNT0F7e3tYDQaQafTQf3JergxdIOisZNUweP3xqGtrY0JjGZHjx0Fx48Oeio6mgt2jbmguaU5rLBtoumpbKBrsNlqbXD9++uULRRNBA+PDEPDqYawAlAYF8nNaJCmxWZ2oPIA9H/XT61IJCzYtN0UtrFgkSeP14FjUBn2yV8m4MyHZ0LuwxcM1/uchAVnpGewhDjcwY00vPsejN68RXdGxj3lho6ODjGHIeB5FG6kMidhwTvSXgpopPH9Rrh96w5F42duZg4+ufCp2PN6OSeK5iQsOH37K9Da0soWm5ZUWCuYWD49OAkLThaCUMqE4hzH6cZ5fgUXCzQlpB2FE1Gw3++nUjS8dI2TGB4TSiTBEaeE9DaS2Ww28iqcO/cxDA4OUk1h1+489oxpRyrcdY2TV8JsLpRzlu8vJ69EgaVAjv3g/Im8CoLAe1gHKaJxQnrY5XJBZnYm1UR8PnbBBwsthazs9W6wK4J+ZPjmsFzmBNfV4Mdj/b91ePTHI/k+n/jj7BX2Mb+RdgtOSEan0wm5u3OpJjE6OgK1R2rBlGICn19JimCyCfEjYLfbIU/sbTVpL6dB3uuvQWaWqgOI9FczwH7WDieOn4Dq6mrm84s/Dl90aLjwOCGCR0Rx2TnZVJPYW1oGPV9cgabTp6G7u5u8EqnbTPBG/h6oP1UPPm/oy8zcn4aVlRXyKKDgy59fDug9Ncqii7APY8Ax5ICuzi4QSgXy4jv7WazrbBd0fNQe0kBwXQ3GRn6+DW63G+Zn55nPTwsOYw8XH0LvV72wM2en5FShLLoIU2LhwQJYCixw+MjhgFXc3/ctdNo7qQbwdtVBmLg3QTWA/dYy8PzroVogDXV1UGg2Q/6efGj5oJn5eOqad2pgdmaWla3lVrgzFvh15IsOezfqlHhe2EeLjhtHU8Gx7d2xwRedQfxw4F7MSUiwj7a8ZFBaIgnW/LTGh4ybVhQXl1BOAxiMevJqIBh3FLXg5eVliiQG5uKH+yKzhbwaCL769VWWlA9d5VuVFImfDdpCzneeZ7m4XfrskhQQSUwwrTEpsV4+qAwMDDC/3xvHIiSxi78tshx4ftDrUlh5bW1NCopoMum+7Okh0UpPP/7zMUU3ZyPobKK21uYWikhotkpyd+WENOb56x8Wi7abPF1/SiXxM29MZc/xkUILRjPBCG9EbQsPfqVoZDwej3w/HyG0laXQM4imglf/fiI3pu6la99cozvE4acrP/UNOYfCPoPH3HBoKhhZ+n1JblTdW4eqD9EdCk2NTXJcLXbsbuAfATWaC0ZWV1fDCkHr6+sP6FU09YvNTEsHokgkRTBHKCoKEBZs+GHA7QvLWVniETOGXTCpgpHeK72yQOxttXH/xQsX6e7NSbpgxCee4qoqKmWB3Eosb8ITcaHGwzMRzJmbm4eag1VgFcrg/uQkeePjmQrWgi3ByeYFEwzwP4NmMKZNG8WYAAAAAElFTkSuQmCC\",\n \"background\": \"#000000\",\n \"image_barcode\": \"JAPER-COMMAND\"\n },\n {\n \"draw\": \"full\",\n \"order\": 6,\n \"justify\": \"middle\",\n \"type\": \"barcode\",\n \"barcodetype\": \"qr\",\n \"qr_error_correction\": \"L\",\n \"barcode_foreground\": \"#FFFFFF\",\n \"barcode_background\": \"#000000\",\n \"imageheight\": 160,\n \"value\": \"https://www.japer.vision/?j=JAPER-PROOF+id:pxbnoR!VOzSFs0wkqt0eUth1jtr1SrY3PIzAT5iVfHEY\",\n \"background\": \"#000000\"\n },\n {\n \"draw\": \"full\",\n \"order\": 7,\n \"justify\": \"middle\",\n \"type\": \"text\",\n \"size\": -8,\n \"value\": \"Proof of JAPER Australia (Systems)\",\n \"pad_top\": 2,\n \"pad_bottom\": 2,\n \"foreground\": \"#FFFFFF\",\n \"background\": \"#000000\"\n },\n {\n \"draw\": \"full\",\n \"order\": 8,\n \"justify\": \"middle\",\n \"type\": \"barcode\",\n \"barcodetype\": \"qr\",\n \"qr_error_correction\": \"L\",\n \"barcode_foreground\": \"#FFFFFF\",\n \"barcode_background\": \"#000000\",\n \"imageheight\": 160,\n \"pad_top\": 32,\n \"value\": \"https://www.japer.vision/?j=JAPER-NAMESPACE\",\n \"background\": \"#000000\"\n },\n {\n \"draw\": \"full\",\n \"order\": 9,\n \"justify\": \"middle\",\n \"type\": \"text\",\n \"size\": -8,\n \"value\": \"JAPER-NAMESPACE\",\n \"pad_top\": 2,\n \"pad_bottom\": 16,\n \"foreground\": \"#FFFFFF\",\n \"background\": \"#000000\"\n },\n {\n \"draw\": \"full\",\n \"order\": 10,\n \"justify\": \"middle\",\n \"type\": \"barcodebutton\",\n \"size\": -4,\n \"barcodebutton_foreground\": \"#FFFFFF\",\n \"barcodebutton_background\": \"#AC43D9\",\n \"barcodebuttontitle\": \"JAPER Mechanism\",\n \"value\": \"JAPER-MECHANISM\",\n \"padding\": 4,\n \"background\": \"#000000\",\n \"background_title\": \"#000000\"\n }\n ]\n }\n}"}],"_postman_id":"8c6b49a1-fd8d-4f56-b5dc-95b5b88687cf"},{"name":"JAPER-COMMAND","event":[{"listen":"test","script":{"id":"3cbb5c75-2ad6-485d-a2c9-62a4f0d2fa23","exec":["pm.test(\"Status code is 200\", function () {"," pm.response.to.have.status(200);","});","","pm.test(\"Response time is less than 3 seconds\", function () {"," pm.expect(pm.response.responseTime).to.be.below(3000);","});"],"type":"text/javascript","packages":{}}}],"id":"0414c926-f58e-41cb-b30e-5ba3c05f1f27","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"auth":{"type":"apikey","apikey":{"basicConfig":[{"key":"key","value":"x-api-key"},{"key":"value","value":"{{JAPER API Key}}"}]},"isInherited":false},"method":"GET","header":[{"key":"japer-aid","value":"{{JAPER Application ID}}"},{"key":"japer-did","value":"{{JAPER Device ID}}"},{"key":"japer-data","value":"JAPER-COMMAND"}],"body":{"mode":"raw","raw":"{\r\n \"japer\": {\r\n \"command\" : \"JAPER-WHO-AM-I\",\r\n }\r\n}"},"url":"https://api.japer.io/v1/x/execute","description":"\n\nReturns the JAPER API Version as JAPER JSON Outcome.
\n
200 = OK
This is the corresponding JAPER App barcode:
\n![\"JAPER-COMMAND\"](\"https://i.imgur.com/KkUQLDn.png\")
\n\nReturns JAPER ISO Time as JAPER JSON Outcome.
\n
200 = OK
This is the corresponding JAPER App barcode:
\n![\"JAPER-ISO-TIME\"](\"https://i.imgur.com/f5iECUC.png\")
\n\nExecutes JAPER-NAMESPACE
\n
200 = JAPER
204 = Not JAPER
https://www.japer.vision/?j=JAPER-NAMESPACE
\nhttps://www.japer.cloud/decrypt?j=JAPER-NAMESPACE
\nhttps://www.japer.cloud/barcode?j=JAPER-NAMESPACE
\n","urlObject":{"host":["https://api.japer.io/v1/x/execute"],"query":[],"variable":[]}},"response":[{"id":"bc7469d4-06a8-4c6b-89c3-ae43fd211d40","name":"JAPER-NEXUS-STATUS","originalRequest":{"method":"GET","header":[{"key":"japer-aid","value":"{{JAPER Application ID}}"},{"key":"japer-did","value":"{{JAPER Device ID}}"},{"key":"japer-data","value":"JAPER-NEXUS-STATUS"}],"body":{"mode":"raw","raw":""},"url":"https://api.japer.io/v1/x/execute"},"status":"OK","code":200,"_postman_previewlanguage":"json","header":[{"key":"Content-Type","value":"application/json","description":"","type":"text"}],"cookie":[],"responseTime":null,"body":"{\n \"outcome\": {\n \"full_allow_landscape\": \"no\",\n \"cache\": 60,\n \"cache_ar\": 60,\n \"cache_full\": 31536000,\n \"type\": \"JAPER\",\n \"lookup\": \"JAPER-NEXUS-STATUS\",\n \"auto_full\": \"no\",\n \"width_full\": 0.98,\n \"full_title_1\": \"Restricted\",\n \"full_title_2\": \"Namespace\",\n \"full_hide_all_buttons\": \"yes\",\n \"full_override_japer\": \"#FF0000\",\n \"ar_border_north_east\": \"#FFFFFF\",\n \"ar_cache_off\": \"yes\",\n \"data\": [\n {\n \"draw\": \"ar\",\n \"order\": 1,\n \"justify\": \"middle\",\n \"type\": \"text\",\n \"size\": -6,\n \"value\": \"Restricted Namespace\"\n },\n {\n \"draw\": \"ar\",\n \"order\": 2,\n \"justify\": \"middle\",\n \"type\": \"text\",\n \"size\": -6,\n \"value\": \"JAPER-NEXUS-STATUS\"\n },\n {\n \"draw\": \"ar\",\n \"order\": 3,\n \"justify\": \"middle\",\n \"type\": \"text\",\n \"size\": -6,\n \"value\": \"Status Code: 403 Forbidden\"\n },\n {\n \"draw\": \"full\",\n \"order\": 4,\n \"justify\": \"middle\",\n \"type\": \"text\",\n \"size\": -4,\n \"value\": \"JAPER-NEXUS-STATUS\",\n \"padding\": 4\n },\n {\n \"draw\": \"full\",\n \"order\": 5,\n \"justify\": \"middle\",\n \"type\": \"text\",\n \"size\": -6,\n \"value\": \"This JAPER Namespace is restricted.\",\n \"padding\": 4\n },\n {\n \"draw\": \"full\",\n \"order\": 6,\n \"justify\": \"middle\",\n \"type\": \"text\",\n \"size\": -12,\n \"value\": \"Status Code: 403 Forbidden\",\n \"padding\": 4\n },\n {\n \"draw\": \"full\",\n \"order\": 7,\n \"justify\": \"middle\",\n \"type\": \"image\",\n \"filetype\": \"png\",\n \"width\": \"44\",\n \"height\": \"44\",\n \"pad_top\": 64,\n \"pad_bottom\": 2,\n \"value\": \"iVBORw0KGgoAAAANSUhEUgAAACwAAAAsCAYAAAAehFoBAAAAAXNSR0IArs4c6QAAAARnQU1BAACxjwv8YQUAAAAJcEhZcwAADsQAAA7EAZUrDhsAAATDSURBVFhH7Zf7SxxXFMf3YVyS2lp/0miMbYQu2kV0THRTayKatXmQYFpjxYjYIpjKakxoCSVNIf9ACVRsIb8UYqU/WQLFdhcT1DTBsEK0RFwUtbGBmmrTNlul0d09nXPn3JnZp7vsbEjAz3KYe8+ZOfc79zV3dfCCsSU42WwJTjZbgiMxNT0F7e3tYDQaQafTQf3JergxdIOisZNUweP3xqGtrY0JjGZHjx0Fx48Oeio6mgt2jbmguaU5rLBtoumpbKBrsNlqbXD9++uULRRNBA+PDEPDqYawAlAYF8nNaJCmxWZ2oPIA9H/XT61IJCzYtN0UtrFgkSeP14FjUBn2yV8m4MyHZ0LuwxcM1/uchAVnpGewhDjcwY00vPsejN68RXdGxj3lho6ODjGHIeB5FG6kMidhwTvSXgpopPH9Rrh96w5F42duZg4+ufCp2PN6OSeK5iQsOH37K9Da0soWm5ZUWCuYWD49OAkLThaCUMqE4hzH6cZ5fgUXCzQlpB2FE1Gw3++nUjS8dI2TGB4TSiTBEaeE9DaS2Ww28iqcO/cxDA4OUk1h1+489oxpRyrcdY2TV8JsLpRzlu8vJ69EgaVAjv3g/Im8CoLAe1gHKaJxQnrY5XJBZnYm1UR8PnbBBwsthazs9W6wK4J+ZPjmsFzmBNfV4Mdj/b91ePTHI/k+n/jj7BX2Mb+RdgtOSEan0wm5u3OpJjE6OgK1R2rBlGICn19JimCyCfEjYLfbIU/sbTVpL6dB3uuvQWaWqgOI9FczwH7WDieOn4Dq6mrm84s/Dl90aLjwOCGCR0Rx2TnZVJPYW1oGPV9cgabTp6G7u5u8EqnbTPBG/h6oP1UPPm/oy8zcn4aVlRXyKKDgy59fDug9Ncqii7APY8Ax5ICuzi4QSgXy4jv7WazrbBd0fNQe0kBwXQ3GRn6+DW63G+Zn55nPTwsOYw8XH0LvV72wM2en5FShLLoIU2LhwQJYCixw+MjhgFXc3/ctdNo7qQbwdtVBmLg3QTWA/dYy8PzroVogDXV1UGg2Q/6efGj5oJn5eOqad2pgdmaWla3lVrgzFvh15IsOezfqlHhe2EeLjhtHU8Gx7d2xwRedQfxw4F7MSUiwj7a8ZFBaIgnW/LTGh4ybVhQXl1BOAxiMevJqIBh3FLXg5eVliiQG5uKH+yKzhbwaCL769VWWlA9d5VuVFImfDdpCzneeZ7m4XfrskhQQSUwwrTEpsV4+qAwMDDC/3xvHIiSxi78tshx4ftDrUlh5bW1NCopoMum+7Okh0UpPP/7zMUU3ZyPobKK21uYWikhotkpyd+WENOb56x8Wi7abPF1/SiXxM29MZc/xkUILRjPBCG9EbQsPfqVoZDwej3w/HyG0laXQM4imglf/fiI3pu6la99cozvE4acrP/UNOYfCPoPH3HBoKhhZ+n1JblTdW4eqD9EdCk2NTXJcLXbsbuAfATWaC0ZWV1fDCkHr6+sP6FU09YvNTEsHokgkRTBHKCoKEBZs+GHA7QvLWVniETOGXTCpgpHeK72yQOxttXH/xQsX6e7NSbpgxCee4qoqKmWB3Eosb8ITcaHGwzMRzJmbm4eag1VgFcrg/uQkeePjmQrWgi3ByeYFEwzwP4NmMKZNG8WYAAAAAElFTkSuQmCC\",\n \"background\": \"#000000\",\n \"image_barcode\": \"JAPER-COMMAND\"\n },\n {\n \"draw\": \"full\",\n \"order\": 8,\n \"justify\": \"middle\",\n \"type\": \"text\",\n \"size\": -8,\n \"value\": \"JAPER Australia (Systems)\",\n \"pad_top\": 2,\n \"pad_bottom\": 2,\n \"foreground\": \"#FFFFFF\",\n \"background\": \"#000000\"\n },\n {\n \"draw\": \"full\",\n \"order\": 9,\n \"justify\": \"middle\",\n \"type\": \"barcode\",\n \"barcodetype\": \"qr\",\n \"qr_error_correction\": \"L\",\n \"barcode_foreground\": \"#FFFFFF\",\n \"barcode_background\": \"#000000\",\n \"imageheight\": 160,\n \"pad_top\": 0,\n \"value\": \"https://www.japer.vision/?j=JAPER-NEXUS-STATUS\",\n \"background\": \"#000000\",\n \"padding\": 0\n },\n {\n \"draw\": \"full\",\n \"order\": 10,\n \"justify\": \"middle\",\n \"type\": \"text\",\n \"size\": -8,\n \"value\": \"JAPER-NEXUS-STATUS\",\n \"pad_top\": 2,\n \"pad_bottom\": 16,\n \"foreground\": \"#FFFFFF\",\n \"background\": \"#000000\"\n },\n {\n \"draw\": \"full\",\n \"order\": 11,\n \"justify\": \"middle\",\n \"type\": \"barcodebutton\",\n \"size\": -4,\n \"barcodebutton_foreground\": \"#FFFFFF\",\n \"barcodebutton_background\": \"#AC43D9\",\n \"barcodebuttontitle\": \"JAPER Command\",\n \"value\": \"JAPER-COMMAND\",\n \"padding\": 4,\n \"background\": \"#000000\",\n \"background_title\": \"#000000\"\n }\n ],\n \"ar_override_japer\": \"#FF0000\"\n }\n}"}],"_postman_id":"818c8117-c281-4373-b9b3-28b7c3d130d2"}],"id":"f6829d8d-a556-4cea-a57d-33351d40b7e4","_postman_id":"f6829d8d-a556-4cea-a57d-33351d40b7e4","description":"","auth":{"type":"noauth","isInherited":true,"source":{"_postman_id":"bf9f1680-493b-4bbb-9088-f23c7aebc929","id":"bf9f1680-493b-4bbb-9088-f23c7aebc929","name":"JAPER Namespace","type":"folder"}}}],"id":"bf9f1680-493b-4bbb-9088-f23c7aebc929","description":"\n\nThe JAPER Namespace, managed exclusively by JAPER Technology, serves as a command protocol and a structured framework for defining and executing operations within the JAPER Ecosystem. Functioning similarly to ICANN's domain system, JAPER namespaces ensure precise command execution through a hierarchical syntax: JAPER-NAMESPACE-SYNTAX+p1:v1+p2:v2
\nAdditionally, as the JAPER App functions as a barcode scanner, JAPER Technology also operates as a barcode registry, linking barcodes to secure commands and resources within the ecosystem.
\nDeeplink: https://www.japer.vision/?j=JAPER-URL+site:www.nasa.gov
\nDeeplink: NASA
\nPDF: JAPER Namespace Manual
\n","auth":{"type":"noauth","isInherited":false},"event":[{"listen":"prerequest","script":{"id":"d40a684a-b2d9-4d2f-a3ab-2d87e3c892ba","type":"text/javascript","exec":[""]}},{"listen":"test","script":{"id":"88fa5cb5-bb12-4442-8d82-d0fa66b2530a","type":"text/javascript","exec":[""]}}],"_postman_id":"bf9f1680-493b-4bbb-9088-f23c7aebc929"}],"id":"7114e528-2111-49ac-8252-28ac8beacdb4","description":"\n\nThe JAPER Ecosystem integrates APIs, websites, and a secure app to deliver advanced digital solutions. The API manages encryption, decryption, validations, and secure data exchange. Websites (japer.technology, japer.cloud, japer.xyz) provide login, utilities, and documentation. The JAPER App offers secure, touch-based access to outcomes and services. Data is stored in JAPER Keyspace for precise, secure management, while Namespace organize commands and outcomes for seamless functionality. Email and validation services ensure robust, compliant communications, enabling end-to-end encryption and control across a unified, scalable ecosystem.
\n","auth":{"type":"noauth","isInherited":false},"event":[{"listen":"prerequest","script":{"id":"63c225d4-6d45-4c41-83f3-6855deaabaa9","type":"text/javascript","exec":[""]}},{"listen":"test","script":{"id":"221eba70-06d1-46f7-9a6b-a9f4ca503201","type":"text/javascript","exec":[""]}}],"_postman_id":"7114e528-2111-49ac-8252-28ac8beacdb4"},{"name":"11. Best Practices","item":[{"name":"Performance Benchmarks","item":[],"id":"0c9f457d-baee-4483-ab32-0dddf5086f70","description":"Gain insight into how the JAPER API operates under different conditions to enhance its application in your projects.
\nJAPER-API-DASHBOARD
Monitor your API usage and performance metrics.
JAPER-API-ALERTS
Set up custom alerts for specific performance thresholds or anomalies.
This needs to expanded.
\n","_postman_id":"cb18af0f-0438-4a1c-b4c4-3ed5a12bd8d4","auth":{"type":"noauth","isInherited":true,"source":{"_postman_id":"f8ad5e90-03e1-47bb-800d-d96bef4744a9","id":"f8ad5e90-03e1-47bb-800d-d96bef4744a9","name":"Developer Support","type":"folder"}}}],"id":"f8ad5e90-03e1-47bb-800d-d96bef4744a9","description":"
JAPER Technology delivers a highly secure, scalable, and resilient encryption and validation ecosystem, leveraging AWS infrastructure to ensure seamless performance across global deployments. Designed for fast, efficient, and trusted access management, JAPER maintains strict security controls, redundancy, and compliance, empowering businesses with real-time encryption, authentication, and secure resource execution.
\nUptime Guarantee: 99.0% uptime per calendar month.
\nResponse Times: Average response time under 333ms for standard endpoints.
\nSupport Response: Guaranteed response within 24 hours for support tickets.
\nJAPER Technology is fully committed to legal compliance, data protection, and regulatory integrity. We adhere to GDPR, industry security standards, and privacy laws, ensuring transparency and ethical data practices. Our operations align with local and international regulations, reinforcing trust, accountability, and lawful usage of our encryption and validation technologies.
\nBy using the JAPER API, you agree to the following terms:
\nUsage Rights: Granted non-exclusive, non-transferable rights to use the API as per your subscription plan.
\nProhibited Activities: Unauthorized distribution of API keys, reverse engineering, and misuse of the API for malicious purposes.
\nTermination: JAPER reserves the right to terminate access for violations of terms.
\nRead Full Terms: JAPER Terms and Conditions
\nJAPER is committed to protecting your data and privacy.
\nData Collection: Details on what data is collected and how it is used.
\nData Usage: Explanation of how your data is processed and stored.
\nData Sharing: Information on third-party data sharing practices, if any.
\nUser Rights: Rights to access, modify, or delete your data.
\nRead Full Privacy Policy: JAPER Privacy Policy
\nJAPER adheres to industry standards and holds various compliance certifications to ensure data security and integrity.
\nJAPER Technology is committed to continuous improvement by integrating feedback and industry best practices, regularly updating its documentation and API features to address user needs and incorporate new functionalities. Through iterative enhancements, changes are implemented in a stable and reliable manner, with a user-centric focus on creating an intuitive, streamlined developer experience.
\nSubmit feedback directly
\n\nParticipate in periodic surveys to share your experience and suggestions
\n\nReport any bugs or issues
\n\n
Permission is hereby granted, free of charge, to any person obtaining a copy of this API documentation and associated Postman collections (the \"JAPER API Documentation\"), to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the JAPER API Documentation, subject to the following conditions:
\nThe above copyright notice, QR barcode and this permission notice shall be included in all copies or substantial portions of the JAPER API Documentation.
\nThe JAPER API Documentation is provided \"as is\", without warranty of any kind, express or implied, including but not limited to the warranties of merchantability, fitness for a particular purpose, and non-infringement. In no event shall the authors or copyright holders be liable for any claim, damages, or other liability, whether in an action of contract, tort, or otherwise, arising from, out of, or in connection with the JAPER API Documentation or the use or other dealings in the JAPER API Documentation.
\nThis license does not grant permission to use the name, trademarks, or branding of JAPER Technology Pty. Ltd. without prior written consent. ABN 44614214863
\nMIT License (JAPER API Documentation Variant)
\n","_postman_id":"e9a86706-1efa-48e8-85de-cef1cb7969a7","auth":{"type":"noauth","isInherited":true,"source":{"_postman_id":"7f17b6c4-6328-42fb-bb77-3221c5f259d2","id":"7f17b6c4-6328-42fb-bb77-3221c5f259d2","name":"api.japer.io","type":"folder"}}}],"id":"7f17b6c4-6328-42fb-bb77-3221c5f259d2","description":"