[Discord] Completing Create Wallet

Development and Support Postman Collection
,
#1
  1. I saw that creating a valid wallet requires that all information below are provided. are we expected to accept all data below from the user when creating wallet.
// Request URL: POST https://sandboxapi.rapyd.net/v1/user

// Message body:
{
    "first_name": "John",
    "last_name": "Doe",
    "ewallet_reference_id": "2021-10-28d",
    "metadata": {
        "merchant_defined": true
    },
    "type": "person",
    "contact": {
        "phone_number": "+14155551234",
        "email": "johndoe@rapyd.net",
        "first_name": "John",
        "last_name": "Doe",
        "mothers_name": "Jane Smith",
        "contact_type": "personal",
        "address": {
            "name": "John Doe",
            "line_1": "123 Main Street",
            "line_2": "",
            "line_3": "",
            "city": "Anytown",
            "state": "NY",
            "country": "US",
            "zip": "12345",
            "phone_number": "+14155551611",
            "metadata": {},
            "canton": "",
            "district": ""
        },
        "identification_type": "DL",
        "identification_number": "1234567890",
        "date_of_birth": "11/22/2000",
        "country": "US",
        "nationality": "US",
        "metadata": {
            "merchant_defined": true
        }
    }
}

I keep getting this error when creating a wallet using the rapyd postman collection. I try filling in the ENV variables from my rapyd acct dashboard, but nothin works.

{
    "status": {
        "error_code": "UNAUTHENTICATED_API_CALL",
        "status": "ERROR",
        "message": "access_key header is not valid",
        "response_code": "UNAUTHENTICATED_API_CALL",
        "operation_id": "eb8f7783-9b53-4d63-8793-d453ba017669"
    }
}
#2

The above error has been fixed. I switched to sandbox mode from my dashboard. But now, it telling me.

{
    "status": {
        "error_code": "UNAUTHENTICATED_API_CALL",
        "status": "ERROR",
        "message": "The API received a request, but the signature did not match. The request was rejected. Corrective action: (1) Remove all whitespace that is not inside a string. (2) Remove trailing zeroes and decimal points, or wrap numbers in a string.",
        "response_code": "UNAUTHENTICATED_API_CALL",
        "operation_id": "2340866e-11f5-4a99-a4a9-8dae729f40cf"
    }
}
#3
  1. If you are working in Postman I would follow this video: Make Your First API Call.
  • All you need to do is download the Postman Collection, input your Sandbox keys (not production) you are set to make calls without the UNAUTHENTICATED_API_CALL error.

If you are working in the hackathon, in Sandbox you do not need to verify your wallet account.

The Wallet example should work, just update the reference ID as needed.

You can also try this:

{
    "first_name": "Samson",
    "last_name": "Smith",
    "email": "",
    "ewallet_reference_id": "Samson-Smith-06227022",
    "metadata": {
        "merchant_defined": true
    },
    "phone_number": "",
    "type": "person",
    "contact": {
        "phone_number": "+14155551311",
        "email": "samson@rapyd.net",
        "first_name": "Samson",
        "last_name": "Smith",
        "mothers_name": "Jane Smith",
        "contact_type": "personal",
        "address": {
            "name": "Samson Smith",
            "line_1": "123 Main Street",
            "line_2": "",
            "line_3": "",
            "city": "Anytown",
            "state": "NY",
            "country": "US",
            "zip": "12345",
            "phone_number": "+14155551111",
            "metadata": {},
            "canton": "",
            "district": ""
        },
        "identification_type": "PA",
        "identification_number": "1234567890",
        "date_of_birth": "11/22/2000",
        "country": "US",
        "nationality": "US",
        "metadata": {
            "merchant_defined": true
        }
    }
}

Here’s a resource if you are working within Postman:

Here are some resources if you are working outside of Postman:

#4

I don’t know which language you are using, but be sure to parse the body properly before generating the signaure.

I had the same problem with PHP and I fixed it adding the JSON_UNESCAPED_SLASHES parametes to json_encode.

json_encode($body, JSON_UNESCAPED_SLASHES);