prawnwire Developers

Headers and metadata

Add application context without replacing the headers Prawnwire owns.

POST/v1/email

Custom headers

Headers is an array of { "Name": "...", "Value": "..." } objects. Both fields must be strings.

Names contain 1 to 100 ASCII letters, digits, or hyphens. Values are a single line of at most 1,000 characters; carriage returns and line feeds are refused. Invalid or reserved headers return ErrorCode 300.

Refused headers

The following names are reserved, case-insensitively:

  • From
  • To
  • Cc
  • Bcc
  • Subject
  • Date
  • Message-ID
  • Reply-To
  • Sender
  • Return-Path
  • Received
  • DKIM-Signature
  • MIME-Version
  • Content-Type
  • Content-Transfer-Encoding

Use ReplyTo for reply routing and the message’s own From, To, Cc, Bcc and Subject fields. Prawnwire writes Date, Message-ID, MIME and signing headers.

Metadata

Metadata is a JSON object with at most 10 fields. Keys are 1 to 20 characters. Values become strings of at most 80 characters.

Use strings for predictable results. Numbers and booleans are accepted and converted with JavaScript’s string conversion. Objects, arrays, and null values are refused. Metadata is returned in activity and message details; it is not a custom email header.

Avoid secrets and unnecessary personal data. A key with email:read can read metadata.

Tags

Tag is an optional string of up to 1,000 characters. Use a stable value such as welcome or receipt, then filter Messages by that value. Tag matching is exact.

Search documentation

Type to search the documentation.