Data Gateway API

Authorize

HEAD /

Used to authorize resources and simultaneously check whether ETag still matches cached ETag.

Status Codes
  • 200 OK – User has access to this resource. Any other response is regarded as being unauthorized. Redirects are not followed.

  • 403 Forbidden – Forbidden. User does not have authorization to view this resource.

  • 404 Not Found – Not Found. Element does not exist or user does not have authorization to know whether this resource exists or not.

Response Headers
  • ETag – RFC2616 revision control. Used to determine if cached data is current.

Load

GET /

Used to download resources which instant3Dhub can then use to build optimized 3D representations.

Example request:

GET / HTTP/1.1
Host: example.com
Status Codes
  • 200 OK

    Success. See the examples below for a full list of possible Content-Types to return.

    Example response:

    HTTP/1.1 200 OK
    Content-Type: model/3mf
    
    binary-data
    

    Example response:

    HTTP/1.1 200 OK
    Content-Type: model/creoview
    
    binary-data
    

    Example response:

    HTTP/1.1 200 OK
    Content-Type: model/fhs
    
    binary-data
    

    Example response:

    HTTP/1.1 200 OK
    Content-Type: model/gltf-binary
    
    binary-data
    

    Example response:

    HTTP/1.1 200 OK
    Content-Type: model/gltf+json
    
    json
    

    Example response:

    HTTP/1.1 200 OK
    Content-Type: model/iges
    
    binary-data
    

    Example response:

    HTTP/1.1 200 OK
    Content-Type: model/iso.step.ap203
    
    binary-data
    

    Example response:

    HTTP/1.1 200 OK
    Content-Type: model/iso.step.ap214
    
    binary-data
    

    Example response:

    HTTP/1.1 200 OK
    Content-Type: model/iso.step.ap242+xml
    
    xml-data
    

    Example response:

    HTTP/1.1 200 OK
    Content-Type: model/obj
    
    binary-data
    

    Example response:

    HTTP/1.1 200 OK
    Content-Type: model/rlxml
    
    xml-data
    

    Example response:

    HTTP/1.1 200 OK
    Content-Type: model/stl
    
    binary-data
    

    Example response:

    HTTP/1.1 200 OK
    Content-Type: model/vnd.autodesk.3ds
    
    binary-data
    

    Example response:

    HTTP/1.1 200 OK
    Content-Type: model/vnd.autodesk.dxf
    
    binary-data
    

    Example response:

    HTTP/1.1 200 OK
    Content-Type: model/vnd.autodesk.fbx
    
    binary-data
    

    Example response:

    HTTP/1.1 200 OK
    Content-Type: model/vnd.autodesk.inventor
    
    binary-data
    

    Example response:

    HTTP/1.1 200 OK
    Content-Type: model/vnd.autodesk.revit
    
    binary-data
    

    Example response:

    HTTP/1.1 200 OK
    Content-Type: model/vnd.avena.rvm
    
    binary-data
    

    Example response:

    HTTP/1.1 200 OK
    Content-Type: model/vnd.blend
    
    binary-data
    

    Example response:

    HTTP/1.1 200 OK
    Content-Type: model/vnd.collada+xml
    
    xml-data
    

    Example response:

    HTTP/1.1 200 OK
    Content-Type: model/vnd.dassault.acis
    
    binary-data
    

    Example response:

    HTTP/1.1 200 OK
    Content-Type: model/vnd.dassault.catia.v4
    
    binary-data
    

    Example response:

    HTTP/1.1 200 OK
    Content-Type: model/vnd.dassault.catia.v5
    
    binary-data
    

    Example response:

    HTTP/1.1 200 OK
    Content-Type: model/vnd.dassault.catia.v6
    
    binary-data
    

    Example response:

    HTTP/1.1 200 OK
    Content-Type: model/vnd.dgn
    
    binary-data
    

    Example response:

    HTTP/1.1 200 OK
    Content-Type: model/vnd.ifc
    
    binary-data
    

    Example response:

    HTTP/1.1 200 OK
    Content-Type: model/vnd.kbl
    
    binary-data
    

    Example response:

    HTTP/1.1 200 OK
    Content-Type: model/vnd.las
    
    binary-data
    

    Example response:

    HTTP/1.1 200 OK
    Content-Type: model/vnd.off
    
    binary-data
    

    Example response:

    HTTP/1.1 200 OK
    Content-Type: model/vnd.parasolid.transmit.binary
    
    binary-data
    

    Example response:

    HTTP/1.1 200 OK
    Content-Type: model/vnd.ply
    
    binary-data
    

    Example response:

    HTTP/1.1 200 OK
    Content-Type: model/vnd.ptc.pro-eng
    
    binary-data
    

    Example response:

    HTTP/1.1 200 OK
    Content-Type: model/vnd.rhino.3dm
    
    binary-data
    

    Example response:

    HTTP/1.1 200 OK
    Content-Type: model/vnd.siemens.nx
    
    binary-data
    

    Example response:

    HTTP/1.1 200 OK
    Content-Type: model/vnd.siemens.openjt
    
    binary-data
    

    Example response:

    HTTP/1.1 200 OK
    Content-Type: model/vnd.siemens.plmxml
    
    xml-data
    

    Example response:

    HTTP/1.1 200 OK
    Content-Type: model/vnd.solidedge
    
    binary-data
    

    Example response:

    HTTP/1.1 200 OK
    Content-Type: model/vnd.solidworks
    
    binary-data
    

    Example response:

    HTTP/1.1 200 OK
    Content-Type: model/x3d-vrml
    
    binary-data
    

    Example response:

    HTTP/1.1 200 OK
    Content-Type: model/x3d+fastinfoset
    
    binary-data
    

    Example response:

    HTTP/1.1 200 OK
    Content-Type: model/x3d+xml
    
    xml-data
    

  • 202 Accepted – Accepted but not yet available.

  • 302 Found – Resource is located elsewhere.

  • 403 Forbidden – Forbidden.

  • 404 Not Found – Not Found.

  • 418 I’m a teapot – Consumer must instantiate a ‘teapot’.

Response Headers
  • ETag – RFC2616 revision control. Used to determine if cached data is current.

  • Content-Type – The content type of the data. Will be used to select an appropriate loader for the data.

  • Content-Disposition – HTTP header which defines a filename for the content. Will be used as a fallback if Content-Type is not given. The file extension will be used as a hint to select an appropriate loader.

  • Retry-After – RFC2616 14.37 describing either an HTTP-date or an integer number of seconds (in decimal) after the time of the response.