๐Ÿ‡ฌ๐Ÿ‡ง
EURO-BOZON
www.fintech.gov.pl
ENG
ENG
  • ๐ŸขEURO-BOZON API
  • ๐Ÿ“–MAIN ASSUMPTIONS
    • โœ…DATA ACCESSIBILITY
    • โœ…TYPES OF SERVICES PROVIDED THROUGH THE API
    • โœ…GENERAL COMMUNICATION DIAGRAM
  • โš™๏ธDATA STRUCTURE IN THE API
    • ๐ŸงพDATA STRUCTURE
    • ๐ŸงพDATA TYPES
    • ๐ŸงพDEFINITIONS AND DESCRIPTION OF JSON FILE PROPERTIES
  • ๐Ÿ”งTECHNICAL SPECIFICATION
    • ๐Ÿ“–TECHNICAL SETUP
    • ๐Ÿ“–NAMING CONVENTION
    • ๐Ÿ“–OPERATIONS
    • ๐Ÿ“–RESPONSE STATUSES
    • ๐Ÿ“–HTTP HEADINGS
    • ๐Ÿ“–FORMAT OF THE MESSAGE RECEIVED
  • ๐Ÿ”SECURITY
    • ๐Ÿ”’HTTPS PROTOCOL
    • ๐Ÿ”’CROSS-ORIGIN RESOURCE SHARING
    • ๐Ÿ”’PROTECTION AGAINST MISUSE
Powered by GitBook
On this page
  1. DATA STRUCTURE IN THE API

DATA STRUCTURE

An example of a complete object of one entity saved in a JSON file

{
        "Company": "Cryptoneyx",
        "Jurisdiction": "Alberta",
        "Date": "09/12/2022",
        "Link": "https://www.securities-administrators.ca/investor-alerts/cryptoneyx-2/",
        "Tag": "cryptoneyx",
        "details": {
            "website": "cryptoneyx.io",
            "url": "https://web.archive.org/web/20220727133545/http://www.cryptoneyx.io/"
        },
        "Old_Company": "Cryptoneyx",
        "Comments": null,
        "Regulator": "Alberta Securities Commission",
        "ifuzz": "cryptoneyx",
        "iweb": "cryptoneyx.io",
        "group": "cryptoneyx",
        "ratio": 100,
        "group_why": "initial",
        "count": 17,
        "id": 1
    },
```
PreviousGENERAL COMMUNICATION DIAGRAMNextDATA TYPES

Last updated 1 year ago

โš™๏ธ
๐Ÿงพ
Page cover image