You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are two issues that need to be addressed to restore Amex connectivity:
As referenced in this issue, Amex has something weird going on with its HTTP Accept header. Apparently they require that this header include application/xml with SOME quality weight - ANY quality weight. Writing Accept: application/xml;q=1 is sufficient, whereas Accept: application/xml fails. Adding anything else with whatever quality doesn't faze Amex; it just needs to see that MIME type somewhere with some quality. A fix for this was committed in a59f1b2
Now that Amex is deigning to speak OFX with you (rather than just dropping you with HTTP errors), you can log in... but it will complain that it can't find the account you're asking for. The STATUS subaggregate within CCSTMTTRNRS contains SEVERITY: ERROR, CODE: 2003 i.e. Account not found. If you send an ACCTINFORQ, it turns out that every ACCTID has all but the last 4 digits of the card# obfuscated. If you use these obfuscated card# verbatim for the ACCTID in your CCSTMTRQ (you can put them into your ofxget.cfg), then the statement request succeeds.
This discussion was converted from issue #101 on December 14, 2020 15:04.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
There are two issues that need to be addressed to restore Amex connectivity:
As referenced in this issue, Amex has something weird going on with its HTTP
Accept
header. Apparently they require that this header includeapplication/xml
with SOME quality weight - ANY quality weight. WritingAccept: application/xml;q=1
is sufficient, whereasAccept: application/xml
fails. Adding anything else with whatever quality doesn't faze Amex; it just needs to see that MIME type somewhere with some quality. A fix for this was committed in a59f1b2Now that Amex is deigning to speak OFX with you (rather than just dropping you with HTTP errors), you can log in... but it will complain that it can't find the account you're asking for. The
STATUS
subaggregate withinCCSTMTTRNRS
containsSEVERITY: ERROR, CODE: 2003
i.e. Account not found. If you send anACCTINFORQ
, it turns out that everyACCTID
has all but the last 4 digits of the card# obfuscated. If you use these obfuscated card# verbatim for theACCTID
in yourCCSTMTRQ
(you can put them into yourofxget.cfg
), then the statement request succeeds.Beta Was this translation helpful? Give feedback.
All reactions