PKPass

From Just Solve the File Format Problem
(Difference between revisions)
Jump to: navigation, search
(Added example links)
(Add required fields)
 
Line 6: Line 6:
 
}}
 
}}
 
'''PKPass''' is the format of tickets, coupons, and loyalty cards used in the iOS Passbook app (and other apps designed to use the format). It is a [[ZIP]]-format archive (but using the .pkpass extension instead of .zip) containing [[JSON]]-format data along with some [[PNG]]-format images. The files within the archive have specific expected names to denote their function.
 
'''PKPass''' is the format of tickets, coupons, and loyalty cards used in the iOS Passbook app (and other apps designed to use the format). It is a [[ZIP]]-format archive (but using the .pkpass extension instead of .zip) containing [[JSON]]-format data along with some [[PNG]]-format images. The files within the archive have specific expected names to denote their function.
 +
 +
== pass.json Structure ==
 +
 +
The <code>pass.json</code> structure is described [https://developer.apple.com/library/archive/documentation/UserExperience/Conceptual/PassKit_PG/Creating.html here] and supported with reference files.
 +
 +
The following fields are described as being required:
 +
 +
* <code>passTypeIdentifier</code>
 +
* <code>serialNumber</code>
 +
* <code>formatVersion</code>
 +
* <code>teamIdentifier</code>
 +
* <code>organizationName</code>
 +
* <code>description</code>
  
 
== Links ==
 
== Links ==

Latest revision as of 13:16, 18 April 2025

File Format
Name PKPass
Ontology
Extension(s) .pkpass
MIME Type(s) application/vnd.apple.pkpass

PKPass is the format of tickets, coupons, and loyalty cards used in the iOS Passbook app (and other apps designed to use the format). It is a ZIP-format archive (but using the .pkpass extension instead of .zip) containing JSON-format data along with some PNG-format images. The files within the archive have specific expected names to denote their function.

[edit] pass.json Structure

The pass.json structure is described here and supported with reference files.

The following fields are described as being required:

  • passTypeIdentifier
  • serialNumber
  • formatVersion
  • teamIdentifier
  • organizationName
  • description

[edit] Links

[edit] Examples links

Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox