<html xmlns="http://www.w3.org/1999/xhtml"><head></head><body><figure class="quote"><figcaption><p><anchor-end xmlns="urn:x-suika-fam-cx:markup:suikawiki:0:9:" a0:anchor="1" xmlns:a0="urn:x-suika-fam-cx:markup:suikawiki:0:9:">[1]</anchor-end> <cite>API Documentation</cite>
(<time>2015-07-28 21:50:59 +09:00</time> 版)
<anchor-external xmlns="urn:x-suika-fam-cx:markup:suikawiki:0:9:" a0:resScheme="URI" xmlns:a0="urn:x-suika-fam-cx:markup:suikawiki:0:9:" a0:resParameter="https://www.shutterfly.com/documentation/AuthAuth.sfly">https://www.shutterfly.com/documentation/AuthAuth.sfly</anchor-external></p></figcaption><blockquote><p>Your app passes the auth token on Shutterfly Open API calls as a special HTTP header, like this:</p><p>X-OPENFLY-Authorization: SFLY user-auth={the auth token}</p><p>for example,</p><p>X-OPENFLY-Authorization: SFLY user-auth=000020654581|1207184770811|610685903d963e98a5aa5766e57fb70340302493</p><p>If it is more convenient, your app can set a classic HTTP Authorization header, like this:</p><p>Authorization: SFLY user-auth=000020654581|1207184770811|610685903d963e98a5aa5766e57fb70340302493</p><p>Please note:</p><p>Shutterfly recommends using X-OPENFLY-Authorization. Your HTTP library may have problems using the Authorization header; it may silently discard your header in favor its own information (even if it has none), which can lead to confusing results.</p></blockquote></figure></body></html>