ZEzerohash
Entity Participants

Submit entity documents

Changed on

Submits a business document on behalf of an entity, or an identity document on behalf of a control person or a beneficial owner of the entity, if you operate a platform on zerohash.

Required documents. An entity can only be approved once every document required for its entity_type and region (US or EU platform) has been uploaded. "One of" means any single document from the group satisfies it.

entity_typeUS platformEU platform
corporationby_laws, proof_of_address, certificate_of_good_standing, one of certificate_of_incorporation / articles_of_incorporationSame as US
llcoperating_agreement, proof_of_address, certificate_of_good_standing, one of articles_of_organization / certificate_of_organizationSame as US
partnershippartnership_agreement, proof_of_address, certificate_of_good_standingexcerpt_of_the_chamber_of_commerce, partnership_agreement, certificate_of_good_conduct_of_entrepreneur, source_of_funds, financial_report, certified_valid_id_of_control_person_and_beneficial_owner, power_of_authorization, id_of_submitter, group_of_companies_chart_including_affiliated_foundation
sole_proprietorshipproof_of_address, certificate_of_good_standing (business_license and business_name_filing_document are optional)excerpt_of_the_chamber_of_commerce, proof_of_residence, certificate_of_good_conduct_of_entrepreneur, source_of_funds, certified_valid_id_of_control_person_and_beneficial_owner
non_profitproof_of_address, proof_of_non_profit_status, one of by_laws / articles_of_organizationlei_certificate, excerpt_of_the_chamber_of_commerce, annual_accounts, power_of_authorization (a power of attorney or a board resolution authorising the submitter), plus legal_opinion when the entity was created with is_complex_structure: true
trustexcerpt_of_the_chamber_of_commerce, proof_of_residence, articles_of_incorporation, articles_of_associations, trust_agreement, certificate_of_good_conduct_of_nnp, source_of_funds, certified_valid_id_of_control_person_and_beneficial_owner, power_of_authorization, id_of_submitterSame as US

Any document without a dedicated type can be uploaded as supporting_document with a free-text document_description; it does not count towards the required set.

post/participants/entity/documents

Request

  • Base URL
    https://api.cert.zerohash.com
  • Auth
    API key in header X-SCX-API-KEY and API key in header X-SCX-PASSPHRASE

Headers

X-SCX-SIGNEDstring required

HMAC-SHA256 signature of the request, base64-encoded. See the Authentication guide for the exact signing formula.

X-SCX-TIMESTAMPstring required
Example:1678901234

Current Unix timestamp in seconds. Must be within 60 seconds of server time or the request is rejected.

Request body

OR
OR
OR
OR
OR
OR

Example request

{
  "document": "aGVsbG8gd29ybGQ=",
  "mime": "pdf",
  "file_name": "supporting_document.pdf",
  "participant_code": "CUST01",
  "document_type": "certificate_of_incorporation",
  "document_description": "Certificate of good standing"
}

Response

Successfully created entity document. Returns the created resource with generated IDs and timestamps.

Example response

{
  "message": {
    "state": "Success",
    "file_name": "supporting_document.pdf",
    "created_at": 1572899177383
  }
}

Changes

  • 47cf70ae701cRevision changes
    • breaking

      removed subschema #1: All accepted fields subschema #2: Entity Supporting Documents subschema #3: Identity Verification Document (Front + Back) from the request body oneOf list

    • info

      added subschema #1: Entity - US Documents subschema #2: Entity - EU Documents subschema #3: Entity User - US Single sided documents subschema #4: Entity User - US Two sided documents (Front + Back) subschema #5: Entity User - EU Single sided documents subschema #6: Entity User - EU Two sided documents (Front + Back) subschema #7: All accepted fields to the request body anyOf list